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

Updated Repository Overview to mark meshery-smi-conformance-action as archived #5833

Merged
merged 1 commit into from
Aug 31, 2024

Conversation

H-A-R-S-H-K
Copy link
Contributor

@H-A-R-S-H-K H-A-R-S-H-K commented Aug 21, 2024

Description

This PR fixes #5832

Screenshots

Screenshot 2024-08-21 at 1 20 29 PM

Notes for Reviewers

Signed commits

  • Yes, I signed my commits.

@l5io
Copy link
Contributor

l5io commented Aug 21, 2024

🚀 Preview for commit acacf32 at: https://66c59d9068e154fb6a036ed4--layer5.netlify.app

@@ -208,7 +208,7 @@ const Repository = () => {
</tr>
</thead>
{backendProject.subdata.map((subdata) => {
const { project,image,language,description,repository,link,maintainers_name } = subdata;
const { project,image,language,description,repository,link,maintainers_name,accessRequired } = subdata;
Copy link
Contributor

Choose a reason for hiding this comment

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

@H-A-R-S-H-K, why these changes?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Ashparshp In the frontend projects subdata this type of code was followed so i thought to make it same for backend.

Copy link
Member

Choose a reason for hiding this comment

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

is this was the ask @H-A-R-S-H-K ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@sudhanshutech well we have to show the status of SMI Conformance repo as archived. To achieve that I added a key "accessRequired" with value as "*archived" in the backend projects subdata and added a div to display that "*archived".

Screenshot 2024-08-24 at 2 33 43 PM

was this not the ask ?

@@ -236,6 +236,7 @@ const Repository = () => {
>
<img className="github-icon" src={github} alt="github-icon" />
</a>
<div className="accessRequired"> { accessRequired != "" ? accessRequired : ""}</div>
Copy link
Contributor

Choose a reason for hiding this comment

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

??

Copy link
Member

Choose a reason for hiding this comment

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

@H-A-R-S-H-K explain this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@sudhanshutech the reason why I made such changes is because the frontend projects subdata follows this type of code to display status of frontend projects such as "*program participation required" on https://layer5.io/community/handbook/repository-overview page.

@Ashparshp
Copy link
Contributor

@H-A-R-S-H-K Thanks for your contribution, let's discuss this on the website's call. Please add this as an agenda item to the meeting minutes.

@Ashparshp
Copy link
Contributor

@H-A-R-S-H-K, You were unavailble in last meeting?

Copy link
Contributor

@Ashparshp Ashparshp left a comment

Choose a reason for hiding this comment

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

Please change the ask only, Also, please attend the meeting to get feedback on the timing.

Let's discuss this during the website call on Monday at 5:30 PM IST (7:00 AM CT). Please consider adding it as an agenda item to the meeting minutes || meeting link.

@vishalvivekm
Copy link
Member

@H-A-R-S-H-K
Thank you, as status is not something we would want to represent as accessRequired we can introduce a new prop called status in repo-data.js and follow existing css and logic of accessRequired.

Alternatively, we could rename accessRequired to something more generic, like additionalInfo.
@H-A-R-S-H-K @Ashparshp will either of you follow up here?

@vishalvivekm vishalvivekm merged commit fa512c6 into layer5io:master Aug 31, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

[Handbook] Update Repository Overview to mark meshery-smi-conformance-action as archived
5 participants