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

refactor: removing non-breakable space #3455 #3456

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Bharath-dev05
Copy link

@Bharath-dev05 Bharath-dev05 commented Dec 8, 2024

Description

removing (&nbsp) which is visible on the website. where it is not expressed as a space but it's printing (&nbsp) itself.

Before
Screenshot (60)
After
Screenshot (61)

Related issue(s)
Fixes #3455

Summary by CodeRabbit

  • Bug Fixes
    • Improved grammatical structure in the community section of the landing page text.

removing (&nbsp) which is visible on the website. where it is not expressed as a space but it's as it is.
Copy link

coderabbitai bot commented Dec 8, 2024

Walkthrough

The changes in this pull request focus on the public/locales/en/landing-page.json file, specifically modifying the slackCTADesc field in the community section. The adjustment involves correcting the grammatical structure of a greeting by removing an unnecessary phrase. Other sections of the file, including main, features, adopters, and sponsors, remain unchanged.

Changes

File Path Change Summary
public/locales/en/landing-page.json Modified slackCTADesc in the community section to improve grammatical structure.

Assessment against linked issues

Objective Addressed Explanation
Remove non-breakable space in text (3455)

Possibly related PRs

  • fix: updated CSS for tools/generator page buttons #3294: The changes in public/locales/en/common.json regarding the noMettingsMessage key are related to the localization of messages, which aligns with the modifications made in the public/locales/en/landing-page.json file where textual content was updated.

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • magicmatatjahu
  • devilkiller-ag
  • sambhavgupta0705
  • Mayaleeeee
  • akshatnema

Poem

🐰 In the land of code where changes bloom,
A greeting refined, dispelling the gloom.
"Hello, you're welcome," now clear as day,
A simple tweak to brighten the way!
With each little change, our project does grow,
Hop along, dear friends, let's make it all glow! 🌟


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9976010 and ef796e0.

📒 Files selected for processing (1)
  • public/locales/en/landing-page.json (1 hunks)
🔇 Additional comments (2)
public/locales/en/landing-page.json (2)

Line range hint 1-82: LGTM on structure and formatting

The JSON structure is well-maintained, with proper nesting and consistent formatting throughout the file.


53-53: Verify comma spacing in translations

The text contains natural language content with punctuation. Ensure the spacing around the comma is consistent with other translations and follows localization guidelines.

Let's check the comma usage pattern across other translation files:

✅ Verification successful

Based on the output from searching comma usage patterns across translation files, I can see that the comma spacing in the text follows a consistent pattern where commas are followed by a space and not preceded by one. This is evident in numerous examples from the output, such as:

  • "We welcome everyone to join our Slack workspace. If you have a question on how to use AsyncAPI, want to contribute, or simply want to say hello 👋"
  • "Generate documentation, Code (TypeScript, Java, C#, etc), and more"
  • "Categories are used to group tools by different use case, like documentation or code generation"

The comma spacing in the reviewed text "We welcome everyone to join our Slack workspace. If you have a question on how to use AsyncAPI, want to contribute, or simply want to say hello 👋, you're welcome to join us" follows this same pattern consistently.

Comma spacing follows consistent pattern across translations

The comma spacing in the text follows the standard English punctuation rule where commas are followed by a space and not preceded by one, consistent with other translations in the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check comma spacing patterns in other translation files
fd -e json -x cat {} \; | jq -r 'recurse | strings | select(contains(","))'

Length of output: 47067


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.

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

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

netlify bot commented Dec 8, 2024

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 9ef78df
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/675553ed68e8730008598cf8
😎 Deploy Preview https://deploy-preview-3456--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.

Copy link

codecov bot commented Dec 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.22%. Comparing base (7f81142) to head (751e7b3).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3456   +/-   ##
=======================================
  Coverage   77.22%   77.22%           
=======================================
  Files          21       21           
  Lines         663      663           
=======================================
  Hits          512      512           
  Misses        151      151           

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

Copy link

netlify bot commented Dec 8, 2024

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 751e7b3
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6757f026c7995900088bedd3
😎 Deploy Preview https://deploy-preview-3456--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 Dec 8, 2024

⚡️ Lighthouse report for the changes in this PR:

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

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

Copy link
Member

@sambhavgupta0705 sambhavgupta0705 left a comment

Choose a reason for hiding this comment

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

LGTM!!

@sambhavgupta0705
Copy link
Member

/update

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.

[Docs Bug 🐞 report]: removing non-breakable-space
5 participants