8000 DRAFT 589-feat: Aws badge widgets by YuliaDemir · Pull Request #842 · rolling-scopes/site · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DRAFT 589-feat: Aws badge widgets #842

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

Closed
wants to merge 14 commits into from
Closed

Conversation

YuliaDemir
Copy link
Collaborator
@YuliaDemir YuliaDemir commented Apr 5, 2025

What type of PR is this? (select all that apply)

  • 🍕 Feature
  • 🐛 Bug Fix
  • 🚧 Breaking Change
  • 🧑‍💻 Code Refactor
  • 📝 Documentation Update

Description

Screenshots, Recordings

Before
image
After
image

Added/updated tests?

  • 👌 Yes
  • 🙅‍♂️ No, because they aren't needed
  • 🙋‍♂️ No, because I need help

[optional] Are there any post deployment tasks we need to perform 8000 ?

[optional] What gif best describes this PR or how it makes you feel?

@github-actions github-actions bot changed the title DRAFT Feat/589 aws badge widgets 589-feat: Aws badge widgets Apr 5, 2025
@YuliaDemir YuliaDemir changed the title 589-feat: Aws badge widgets DRAFT 589-feat: Aws badge widgets Apr 5, 2025
@YulikK YulikK added the feature New feature or request label Apr 8, 2025
@YulikK YulikK added this to RS Site Apr 8, 2025
@YulikK YulikK moved this to Review in RS Site Apr 8, 2025
Copy link
github-actions bot commented Apr 9, 2025

Lighthouse Report:

  • Performance: 68 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

@YulikK YulikK force-pushed the feat/589-aws-badge-widgets branch from ed632ca to ed1f3aa Compare April 10, 2025 07:46
@YulikK
Copy link
Collaborator
YulikK commented Apr 10, 2025

run visual now

Copy link

Lighthouse Report:

  • Performance: 96 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

< 8000 /div>
Copy link

Lighthouse Report:

  • Performance: 76 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

@YulikK YulikK changed the title DRAFT 589-feat: Aws badge widgets 589-feat: Aws badge widgets Apr 10, 2025
@@ -30,18 +23,14 @@ export {
RS_DOCS_EN_LINK,
RS_DOCS_TELEGRAM_CHATS_LINK,
} from './communication.data';

export { type Benefit } from './benefit-mentorship.data';
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
export { type Benefit } from './benefit-mentorship.data';
export type { Benefit } from './benefit-mentorship.data';

Copy link
Collaborator

Choose a reason for hiding this comment

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

@ansivgit We should probably add a corresponding eslint rule

Copy link
Collaborator

Choose a reason for hiding this comment

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

Now this component can't be used anywhere else. I suggest replacing it with the Badge component, remove aws name-parts from it and moving the all data (title, text, badge params) to the folder dev-data

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

@YulikK YulikK requested a review from ansivgit May 2, 2025 18:50
Copy link
github-actions bot commented May 4, 2025

Lighthouse Report:

  • Performance: 52 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

Copy link
Collaborator

Choose a reason for hiding this comment

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

It's not .data, it's component. Put it in shared folder

import { Paragraph } from '@/shared/ui/paragraph';
import { WidgetTitle } from '@/shared/ui/widget-title';

type BadgeData = {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
type BadgeData = {
type BadgeProps = {

return (
<section
className={cx(data.className, 'container')}
data-testid={data.className}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
data-testid={data.className}
data-testid="badge"

image: StaticImageData;
alt: string;
className: string;
styles: { [key: string]: string };
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we need styles prop here? We could use .scss as we do in other shared components

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok, I've read the comments, and I will make the changes.

Copy link
Collaborator

Choose a reason for hiding this comment

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

You could use this component as an example of file & folder structure src/shared/ui/logo

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I guess i did it.

Copy link

Lighthouse Report:

  • Performance: 64 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

};

export const Badge = (data: BadgeProps) => {
const cx = classNames.bind(styles);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please move cx outside the component, similar to how it's handled in other components


return (
<section
className={cx('badge', 'container')}
Copy link
Collaborator

Choose a reason for hiding this comment

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

badge className seems redundant to me

Copy link
Collaborator

Choose a reason for hiding this comment

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

Since AwsBadge is just a regular Badge component, I don't see a reason for adding separate tests for it

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I believe I've made all the necessary changes.

@KristiBo KristiBo removed this from RS Site May 19, 2025
Copy link

Lighthouse Report:

  • Performance: 75 / 100
  • Accessibility: 96 / 100
  • Best Practices: 100 / 100
  • SEO: 100 / 100

View detailed report

@YulikK YulikK changed the title 589-feat: Aws badge widgets DRAFT 589-feat: Aws badge widgets May 26, 2025
@YulikK
Copy link
Collaborator
YulikK commented May 27, 2025

Changes have been moved to contentful, PR can be closed

@YulikK YulikK closed this May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non course data in the courses content map
6 participants
0