Skip to content
This repository has been archived by the owner on Sep 7, 2024. It is now read-only.

Add 3 new webinars #835

Merged
merged 1 commit into from
Dec 19, 2023
Merged

Add 3 new webinars #835

merged 1 commit into from
Dec 19, 2023

Conversation

Susmita-Dey
Copy link
Contributor

@Susmita-Dey Susmita-Dey commented Dec 19, 2023

Fixes Issue

This PR fixes the following issues:

closes #issue-number

Changes proposed

Here comes all the changes proposed through this PR

Check List (Check all the boxes which are applicable)

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • All new and existing tests passed.
  • This PR does not contain plagiarized content.
  • The title of my pull request is a short description of the requested changes.

Screenshots

Add all the screenshots which support your changes

Summary by CodeRabbit

  • New Features

    • Introduced new webinar content with detailed information for upcoming events.
    • Enhanced webinar cards with conditional linking based on available video content.
  • Refactor

    • Streamlined the import of link components in webinar cards.
  • Documentation

    • Added descriptions for new webinar-related modules and objects.

Copy link

coderabbitai bot commented Dec 19, 2023

Walkthrough

The project has been updated with enhancements focusing on webinar content management. Modifications include a restructured import pattern for link components, an update to the WebinarCard for dynamic link handling, and the introduction of new webinar-related objects with comprehensive details. The content index is also expanded to incorporate these latest webinar entries.

Changes

File Path Changes
src/components/Cards/WebinarCard.jsx Updated imports for link components; added conditional href.
src/content/Webinars/... Added new webinar objects: DevProductivityAIEra, PulumiWebinar, StateOfJava; updated content index to include these webinars.

🐇✨
To the code we hop and leap,
New webinars in the keep.
With links that smartly bind,
Our updates, you'll joyfully find. 🎉🥕
🐇✨

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 X ?


Tips

Chat with CodeRabbit Bot (@coderabbitai)

  • You can reply to a review comment made by CodeRabbit.
  • You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
  • You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

Copy link

livecycle bot commented Dec 19, 2023

kunal

Your Livecycle playground is ready 🎉.

Playground version up to date (f2d018c)

Invite team members and start collaborating 💪

Check the box and click "invite" to invite collaborators

  • Kunal Kushwaha

invite

Click here to invite the rest of your team.

@github-actions github-actions bot added the team label Dec 19, 2023
@Susmita-Dey Susmita-Dey merged commit fa8370e into WeMakeDevs:main Dec 19, 2023
6 checks passed
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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 2ef4528 and d6887cd.
Files ignored due to filter (3)
  • src/assets/webinars/Maximising-Developer-Productivity-AI-Era.png
  • src/assets/webinars/pulumi-webinar.jpg
  • src/assets/webinars/state-of-java.jpg
Files selected for processing (5)
  • src/components/Cards/WebinarCard.jsx (2 hunks)
  • src/content/Webinars/DevProductivityAIEra.js (1 hunks)
  • src/content/Webinars/PulumiWebinar.js (1 hunks)
  • src/content/Webinars/StateOfJava.js (1 hunks)
  • src/content/Webinars/index.content.js (2 hunks)
Additional comments: 7
src/components/Cards/WebinarCard.jsx (2)
  • 5-5: Refactoring the imports to use a collective source improves modularity and maintainability.

  • 8-10: The conditional logic for setting the href attribute is clear and concise. Ensure that the slug format for YouTube links and the routing path for internal links are consistent across the application.

Verification successful

The verification process has not found any other instances of the YouTube slug format or the internal routing path for webinars being used elsewhere in the codebase. The YouTube slug format appears to be unique to the WebinarCard.jsx component, and the internal routing path for webinars is also only used in this component. Therefore, the conditional logic for setting the href attribute in WebinarCard.jsx is consistent within the context of its usage.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the YouTube slug format is consistent
rg --type js 'https://www.youtube.com/watch?v='

# Verify that the internal routing path is consistent
rg --type js '/events/webinar/'

Length of output: 151



Script:

#!/bin/bash
# Search for dynamic construction of YouTube URLs
ast-grep --lang javascript --pattern $'$_.includes("https://www.youtube.com/watch?v=")'

# Search for dynamic construction of internal routing paths
ast-grep --lang javascript --pattern $'`/events/webinar/${$_}`'

Length of output: 2205

src/content/Webinars/DevProductivityAIEra.js (1)
  • 1-10: The webinar object for "Maximising Developer Productivity in the AI Era" is well-structured and contains all necessary attributes. Ensure that the time attribute is in a format that is consistent with the rest of the application and that the poster asset is correctly linked.
Verification successful

The verification process has confirmed that:

  • The time attribute format used in DevProductivityAIEra.js is consistent with the format used in other webinar objects within the codebase.
  • The poster asset for the "Maximising Developer Productivity in the AI Era" webinar exists in the expected directory.

Based on the information provided by the executed shell scripts, the initial review comment is supported by the evidence. The webinar object structure is correct, and the necessary attributes are present and consistent with the application's standards.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the time format is consistent across webinar objects
ast-grep --lang javascript --pattern $'const $$$ = {
  $$$
  time: $_,
  $$$
}'

# Verify that the poster asset exists
fd 'Maximising-Developer-Productivity-AI-Era.png' src/assets/webinars/

Length of output: 53508

src/content/Webinars/PulumiWebinar.js (1)
  • 1-32: The PulumiWebinar object is comprehensive and includes a detailed structure with external content imports. Verify that the imported components (IndividualWebinarCompletedPageHeader, IndividualWebinarPageFAQ) are used consistently and that the register attribute matches the expected format or identifier used in the application.
Verification successful

The search results confirm that the IndividualWebinarCompletedPageHeader and IndividualWebinarPageFAQ components are consistently used across various webinar-related JavaScript files in the project. Each webinar object seems to have a header and faq property that is assigned these components, respectively.

Additionally, the register attribute is used in a consistent manner across different webinar objects. Each register property is set to a string that appears to be a unique identifier for the webinar, which matches the pattern seen in the PulumiWebinar.js file.

Based on the information provided, there are no inconsistencies or issues with the usage of the imported components or the register attribute in the PulumiWebinar.js file.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the imported components are used consistently
rg 'IndividualWebinarCompletedPageHeader' --type js
rg 'IndividualWebinarPageFAQ' --type js

# Verify that the register attribute is consistent
rg 'register:' --type js

Length of output: 8140

src/content/Webinars/StateOfJava.js (1)
  • 1-35: The StateOfJava webinar object is consistent with the structure of other webinar objects. Ensure that the time attribute is in the correct format and that the poster asset exists. Additionally, verify that the slug is unique and does not conflict with existing routes.
Verification successful

The executed scripts have provided the following information:

  1. The time attribute format in StateOfJava.js is consistent with other webinar objects in the codebase, such as PulumiWebinar.js, DevProductivityAIEra.js, and others. They all follow a similar pattern, which is a full date with time and timezone specified.

  2. The poster asset state-of-java.jpg exists in the directory src/assets/webinars/.

  3. The slug state-of-java-in-2024 is unique within the JavaScript files in the repository, as it only appears in StateOfJava.js.

Based on this information, the StateOfJava webinar object is correctly structured, the time attribute follows the established format, the poster asset exists, and the slug is unique. The verification is successful.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the time format is consistent across webinar objects
ast-grep --lang javascript --pattern $'const $$$ = {
  $$$
  time: $_,
  $$$
}'

# Verify that the poster asset exists
fd 'state-of-java.jpg' src/assets/webinars/

# Verify that the slug is unique
rg 'state-of-java-in-2024' --type js

Length of output: 53560

src/content/Webinars/index.content.js (2)
  • 7-16: The imports for the new webinars are correctly added. Ensure that the paths are correct and that there are no typos in the import statements.
Verification successful

The shell script output confirms that the import paths for DevProductivityAIEra, PulumiWebinar, and StateOfJava are correct, as the files exist in the specified directory.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the import paths are correct
fd 'DevProductivityAIEra.js' src/content/Webinars/
fd 'PulumiWebinar.js' src/content/Webinars/
fd 'StateOfJava.js' src/content/Webinars/

Length of output: 255

* 54-74: The `webinar` array has been correctly extended to include the new webinars. Ensure that the structure of the new entries matches the existing ones and that all necessary attributes are present.
Verification successful

The output from the executed script shows the structure of the webinar array entries in src/content/Webinars/index.content.js. It confirms that the new webinar entries (DevProductivityAIEra, PulumiWebinar, and StateOfJava) have been added with a consistent structure, including fields such as img, title, description, slug, and in some cases, details and time.

The presence of additional entries with similar structures, including fields like details and time, suggests that the new entries are consistent with the existing pattern in the webinar array.

Based on the provided output, it appears that the structure of the new webinar entries matches the existing ones and includes all necessary attributes as per the existing pattern in the array.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify that the structure of webinar entries is consistent
ast-grep --lang javascript --pattern $'export const webinar = [
  {
    img: $_,
    title: $_,
    description: $_,
    $$$
  },
  $$$
]'

Length of output: 12130

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

Successfully merging this pull request may close these issues.

1 participant