-
Notifications
You must be signed in to change notification settings - Fork 0
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
Support to display workspace feature configured with wildcard #186
Conversation
Codecov Report
@@ Coverage Diff @@
## workspace #186 +/- ##
=============================================
+ Coverage 66.09% 66.12% +0.02%
=============================================
Files 3420 3420
Lines 65747 65753 +6
Branches 10590 10590
=============================================
+ Hits 43456 43478 +22
+ Misses 19650 19634 -16
Partials 2641 2641
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
// expanded to array of individual feature id, if the feature hasn't changed, we will | ||
// set the feature config back to the original value so that category wildcard won't | ||
// expanded to feature ids | ||
formData.features = defaultValues?.features ?? []; |
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.
Is that means the wildcard match will be removed after add some new feature ids?
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.
Yes, that makes sense to me as that's what the user selected
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.
OK. Just wonder if we can support wildcard for the feature category level. Which means if user select a feature category, we will store wildcard feature rule. If they remove some one, we will change to feature ids.
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.
Sounds good to me, we could have an improvement ticket for this.
1. In workspace update page, support to display workspace feature configured with wildcard. 2. Fixed an issue which generateWorkspacePermissionError return void 3. Fixed an issue which workspace route validation failed due to missing permission mode in schema Signed-off-by: Yulong Ruan <ruanyl@amazon.com>
Signed-off-by: Yulong Ruan <ruanyl@amazon.com>
b0731a4
to
fe976fa
Compare
* Support to display workspace feature configured with wildcard 1. In workspace update page, support to display workspace feature configured with wildcard. 2. Fixed an issue which generateWorkspacePermissionError return void 3. Fixed an issue which workspace route validation failed due to missing permission mode in schema Signed-off-by: Yulong Ruan <ruanyl@amazon.com> * update dependence array Signed-off-by: Yulong Ruan <ruanyl@amazon.com> --------- Signed-off-by: Yulong Ruan <ruanyl@amazon.com> (cherry picked from commit 25b9e5c) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Issues Resolved
Screenshot
Testing the changes
Check List
yarn test:jest
yarn test:jest_integration
yarn test:ftr