-
Notifications
You must be signed in to change notification settings - Fork 2.8k
update console permissions #1658
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
Conversation
|
Review app for commit 92340ab deployed to Heroku: https://hge-ci-pull-1658.herokuapp.com |
|
Review app for commit 60d8909 deployed to Heroku: https://hge-ci-pull-1658.herokuapp.com |
praveenweb
left a comment
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.
LGTM
Depending on feedback, we can bring back trash icon in a different form in a later update.
|
Review app for commit 8d6658f deployed to Heroku: https://hge-ci-pull-1658.herokuapp.com |
|
Review app https://hge-ci-pull-1658.herokuapp.com is deleted |
|
Review app for commit 92baf9c deployed to Heroku: https://hge-ci-pull-1658.herokuapp.com |
<!-- The PR description should answer 2 important questions: --> ### What Add validation for command output types This PR adds validation to ensure that command output types reference valid types in the schema. A new flag `require_valid_command_output_type` is introduced to control this behavior. ### How Key changes: - Add validation in command resolution to check if output type exists - Add new `InvalidCommandOutputType` issue type - Add new compatibility flag `RequireValidCommandOutputType` (compatibility date TBD) - Add tests for invalid output type case V3_GIT_ORIGIN_REV_ID: 88bd30a09431ce85c2d7b68e7aba507508088bcb
Description
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
Solution and Design
Type
Checklist: