Skip to content

feat(client): unhidden top banner #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 5, 2025
Merged

Conversation

DamianBrzezinskiHoA
Copy link
Contributor

@DamianBrzezinskiHoA DamianBrzezinskiHoA commented May 5, 2025

Summary by CodeRabbit

  • New Features
    • Updated the top banner to promote the Angular Spring Camp event with new text and a registration link.
  • Bug Fixes
    • Re-enabled the top banner display on the main shell for improved event visibility.

Copy link

coderabbitai bot commented May 5, 2025

Walkthrough

This change updates the promotional banner displayed in the application. The TopBannerComponent is modified to advertise the Angular Spring Camp event with new text and a different URL. In the RootShellComponent, the previously commented-out static TopBannerComponent is re-enabled by uncommenting its usage in the template and adding it back to the imports array. No changes are made to the public APIs of the affected components; all modifications are internal to the components’ templates and logic.

Changes

File(s) Change Summary
libs/blog/ad-banner/ui/src/lib/top-banner.component.ts Updated the banner link to a new event page with UTM parameters; changed banner text to promote Angular Spring Camp.
libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts Re-enabled static TopBannerComponent by uncommenting its usage in the template and adding it to the imports array.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RootShellComponent
    participant TopBannerComponent

    User->>RootShellComponent: Loads application shell
    RootShellComponent->>TopBannerComponent: Renders static event banner
    TopBannerComponent-->>User: Displays Angular Spring Camp promotional banner
Loading

Possibly related PRs

  • #439: The main PR re-enables and updates the TopBannerComponent usage in RootShellComponent, directly reversing the changes made in the retrieved PR that disabled the banner by commenting it out and removing its import.
  • #437: Both PRs modify the same TopBannerComponent by updating the banner's anchor URL and displayed text to promote Angular Spring Camp events, indicating a direct continuation or refinement of the banner content.
  • #405: Originally introduced the TopBannerComponent and added it to the exports and RootShellComponent; this PR updates the same component and its integration in the shell.

Poem

🐇
A banner hops up, bright and new,
With Angular Spring Camp in full view!
No more carousels spinning round,
Just a single leap, event-bound.
Click the link, don’t miss the show—
The rabbit says, “It’s time to go!”
🌱


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02369c7 and a1d3725.

📒 Files selected for processing (2)
  • libs/blog/ad-banner/ui/src/lib/top-banner.component.ts (1 hunks)
  • libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • libs/blog/ad-banner/ui/src/lib/top-banner.component.ts
  • libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@valueadd-robot
Copy link

PR is detected, will deploy to dev environment

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts (2)

34-40: Banner carousel rendering commented out.

The conditional rendering logic for the banner carousel has been commented out rather than removed.

If this change is intended to be permanent, consider removing the commented code rather than keeping it commented out to reduce code bloat and improve maintainability.


56-69: Slider store logic commented out.

The computed properties and store related to the banner carousel have been commented out.

If this change is intended to be permanent, consider removing the commented code rather than keeping it commented out to improve code maintainability.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96c5b75 and 02369c7.

📒 Files selected for processing (2)
  • libs/blog/ad-banner/ui/src/lib/top-banner.component.ts (1 hunks)
  • libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts (4 hunks)
🔇 Additional comments (6)
libs/blog/ad-banner/ui/src/lib/top-banner.component.ts (1)

9-16: Banner updated with Angular Spring Camp 2025 information.

The banner has been correctly updated to promote the Angular Spring Camp 2025 event, with appropriate UTM parameters for tracking in the URL and clear event details in the text.

libs/blog/shell/feature-shell-web/src/lib/root-shell.component.ts (5)

17-17: TopBannerComponent import added.

Import for TopBannerComponent has been correctly added to the imports list.


23-23: Static top banner component added to template.

The static top banner component has been added to replace the dynamic banner carousel.

Note: The template reference variable #topBanner is defined but doesn't appear to be used elsewhere in the component.


52-52: TopBannerComponent added to component imports.

TopBannerComponent has been properly added to the component's imports array, which is necessary for using it in the template.


74-74: adBannerVisible property still used but hardcoded to false.

The adBannerVisible computed property is hardcoded to false but is still used in the layout and viewport offset logic.

Since the top banner is now visible, should adBannerVisible return true instead? This would affect the layout (mt-20 class) and the viewport offset calculation in the effect.


101-101: Store data fetch commented out.

The call to sliderStore.getData() has been commented out, which is consistent with disabling the banner carousel functionality.

@valueadd-robot
Copy link

Deployed to dev environment
Branch: feat/enable-top-banner
BFF URL: https://0f5843b5-blog-bff-dev.contact-ef8.workers.dev
Deploy URL: https://82d7296e.angular-love-client.pages.dev
Alias URL: https://feat-enable-top-banner.angular-love-client.pages.dev

@valueadd-robot
Copy link

PR is detected, will deploy to dev environment

@DamianBrzezinskiHoA DamianBrzezinskiHoA changed the title feat(client): unhidden top banner, hidden al-banner feat(client): unhidden top banner May 5, 2025
@valueadd-robot
Copy link

Deployed to dev environment
Branch: feat/enable-top-banner
BFF URL: https://dd9b29a4-blog-bff-dev.contact-ef8.workers.dev
Deploy URL: https://6683ed99.angular-love-client.pages.dev
Alias URL: https://feat-enable-top-banner.angular-love-client.pages.dev

@DDonochVA DDonochVA merged commit b90e11a into main May 5, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants