-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Created Context for Qualifier 1 Page #502
Conversation
…aion on COP JSON structure
…to QualifiersContext
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall really good job! Plz just try to change the structure of the json to not include any whitespace in the variable names. Its not a big deal but itll help with visibility,
mkdocs/docs/developer/frontend.md
Outdated
- **COP (Community of Practice) JSON Structure:** The COP data represents different communities of practice within our organization, each consisting of various roles and descriptions. Below is the JSON structure of the COP data for QualifierPageRoles.tsx: | ||
``` | ||
{ | ||
COPs: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change the structure to not have whitespaces ? Instead of "Back End Developer" , we should use "Back_End_Developer" ... etc. plz
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @JimmyJuarez10 , Thanks for your feedback! I can change the formatting in this JSON structure.
I wanted to confirm with you:
Should I also change the format of strings in frontend/src/api_data/copData.ts?
If so, that means I should replace all underscores with spaces on line 145 in frontend/src/pages/QualifierPage/QualifierPageRoles.tsx, correct? Currently, the strings are used as text values for each Chip.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mmm to clarify , right now we are reading the value off the chip and storing that in the json ?
Fixes #500
Changes
Screenshots, if applicable
Title