Skip to content
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

feat: add paris ticket banner #3363

Merged
merged 4 commits into from
Nov 11, 2024
Merged

feat: add paris ticket banner #3363

merged 4 commits into from
Nov 11, 2024

Conversation

thulieblack
Copy link
Member

@thulieblack thulieblack commented Nov 5, 2024

Ticket banner for paris

Summary by CodeRabbit

  • New Features
    • Updated banner to promote the "AsyncAPI Conference" in Paris, scheduled for December 5, 2024, with new details including title, date, location, and call to action.
  • Chores
    • Enhanced ESLint configuration by adding Jest environment settings and refining rules for specific file types.

Copy link

coderabbitai bot commented Nov 5, 2024

Walkthrough

The changes involve updates to the shouldShowBanner function in components/campaigns/banners.ts, specifically modifying the banners array to reflect new event details. The function's logic remains unchanged, but the banner now promotes the "AsyncAPI Conference" scheduled for December 5, 2024, replacing the previous event details for the "AsyncAPI Online Conference'24."

Changes

File Change Summary
components/campaigns/banners.ts Updated the banners array to reflect new event details for "AsyncAPI Conference" in Paris on December 5, 2024, replacing the previous event.
.eslintrc Added jest environment for linting and modified the max-len rule to be off for files in components/logos/*.

Possibly related PRs

  • feat: create banner for online conf #3312: The changes in this PR also modify the shouldShowBanner function in components/campaigns/banners.ts, indicating a direct relationship in terms of function modifications and the handling of the banners array.

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • magicmatatjahu
  • anshgoyalevil
  • Mayaleeeee
  • asyncapi-bot-eve
  • devilkiller-ag
  • sambhavgupta0705
  • BhaswatiRoy
  • J0SAL
  • TRohit20
  • VaishnaviNandakumar

🐇 In Paris, the banners now gleam,
For AsyncAPI, we chase the dream.
With dates anew and a call to attend,
Join us, dear friends, the fun won’t end!
So hop on over, don’t delay,
For a conference bright on a December day! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d4ec91a and 3478e23.

📒 Files selected for processing (2)
  • .eslintrc (2 hunks)
  • components/campaigns/banners.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/campaigns/banners.ts
🔇 Additional comments (2)
.eslintrc (2)

12-13: LGTM! Good addition of Jest environment.

Adding the Jest environment is a good practice as it enables proper linting for test files and prevents false positives for Jest-specific globals.


317-317: LGTM! Appropriate override for logo components.

The override to disable max-len for logo components is well-placed and makes sense, as SVG/logo files often contain necessarily long lines.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.

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 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.

Copy link

netlify bot commented Nov 5, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 3478e23
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6730f25cfc7b2a0008c80994
😎 Deploy Preview https://deploy-preview-3363--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Nov 5, 2024

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 45
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3363--asyncapi-website.netlify.app/

@thulieblack
Copy link
Member Author

@akshatnema 😁😁

@akshatnema
Copy link
Member

@coderabbitai full review

Copy link

coderabbitai bot commented Nov 8, 2024

✅ Actions performed

Full review triggered.

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: 1

🧹 Outside diff range and nitpick comments (2)
components/campaigns/banners.ts (2)

Line range hint 7-7: Fix typo in comment

There's a spacing issue in the comment: "G et" should be "Get".

-  const currentDate = new Date(); // G et the current date
+  const currentDate = new Date(); // Get the current date

Line range hint 7-15: Consider simplifying the function

The function could be more concise by using a single return statement.

 export function shouldShowBanner(cfpDeadline: string) {
   const currentDate = new Date();
   const deadline = new Date(cfpDeadline);
-  if (currentDate > deadline) {
-    return false;
-  }
-  return true;
+  return currentDate <= deadline;
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 5ea47bb and d4ec91a.

📒 Files selected for processing (1)
  • components/campaigns/banners.ts (1 hunks)
🔇 Additional comments (2)
components/campaigns/banners.ts (2)

26-26: Verify the conference URL accessibility

Please ensure the conference URL is active and redirects correctly to the tickets section.


20-26: Verify the tight deadline window

The CFP deadline (December 1st) is only 4 days before the event (December 5th). This might not give enough time for last-minute registrations and event preparations.

Consider extending the visibility of the banner even after the deadline to allow last-minute registrations.

Comment on lines 20 to 26
title: "AsyncAPI Conference",
city: 'Paris Edition',
dateLocation: '5th of December, 2024 | France, Paris',
cfaText: 'Get Your Tickets',
eventName: 'the AsyncAPI Conf in Paris',
cfpDeadline: '2024-12-01T06:00:00Z',
link: 'https://conference.asyncapi.com/#tickets'
Copy link

@coderabbitai coderabbitai bot Nov 8, 2024

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider lazy loading the banner for better performance

Given the low Lighthouse performance score (46), consider implementing lazy loading for the banner component to improve initial page load time.

Example implementation:

// In a separate file: components/campaigns/AsyncBanner.tsx
import dynamic from 'next/dynamic'

export const AsyncBanner = dynamic(() => import('./Banner'), {
  loading: () => null,
  ssr: false
})

Copy link
Member

Choose a reason for hiding this comment

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

We will handle this in a separate issue

Copy link

Choose a reason for hiding this comment

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

@akshatnema, understood. Would you like me to create a new GitHub issue to track this optimization for future implementation?

Copy link
Member

Choose a reason for hiding this comment

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

I think there is an existing issue for this

Copy link

Choose a reason for hiding this comment

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

@akshatnema, understood. Thank you for letting me know that there is an existing issue for this.

akshatnema
akshatnema previously approved these changes Nov 10, 2024
Copy link

codecov bot commented Nov 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.77%. Comparing base (f6757b4) to head (3478e23).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3363   +/-   ##
=======================================
  Coverage   67.77%   67.77%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          450      450           
  Misses        214      214           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@akshatnema
Copy link
Member

/rtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants