-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Create a reusable component for role category and migrate opportunity to use it #228
base: main
Are you sure you want to change the base?
Conversation
] | ||
} | ||
} | ||
} |
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 @chungthuang I didn't understood very well why use it as a Enum inside a Component instead of use it just as a enum.
Could you explain ?
Follow bellow 2 different attributes with different behaviors, roleType and roleCategory.
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.
roleType
might not be the best name, but it means the name of the role. It's defined in https://github.com/dev-launchers/strapiv4/pull/228/files#diff-8385a8efd2cb2543e792c4e88ce7a586cf150d72489cfe80e3ba2a3b03c4a6a9R59-R73.
For example, both Front-End Developer
and Back-End Developer
will fall under Developer
roleCategory.
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.
Hmm maybe it is something like a subcategory ?
Let me know if it is correct.
We can create a model roleCategory that has the attribute category.
But to make it practical we can use it as a component ?
ad03b8e
to
ad83408
Compare
ad83408
to
a395148
Compare
|
Resolves #227