-
Notifications
You must be signed in to change notification settings - Fork 94
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
Provide ability to disable validation of profiles setting #922
Comments
Here is the flow I would like and screen shots of what I have so far. The only problem I am having at the moment deals with the bottom block/scenario where the user has Disabled/Enabled via a right click action and should get the alternate option the next time they right click on the session/profile. The regex I have for when at this moment only reads the global setting of true or false, I am not familiar with regex and am not sure how to go about checking the profile's validation setting which is stored in a new |
Cool! Thank you @JillieBeanSim for this. Question, I have the Global Validation checked. If I disable the validation for Profile A and then close VSC, will the Global Validation take effect once I open VSCode? or ZE can detect that I have disabled the validation in Profile A before? |
@jellypuno upon refresh or restart of vs code all profiles will revert back to global setting. Refreshing of a tree view will keep the alternate setting. Should refreshing a tree view revert back to global setting as well? What do you think? |
Issue #922 Ability to Disable Profile Validation (only codecov/project failing)
Is your feature request related to a problem? Please describe.
This is the more involved fix for Pete's issue, #918.
Describe the solution you'd like
As a user, I would like to be able to disable the validation of profiles setting since I may be working with cloud instances (zD&Ts) or particularly slow LPARS that make this process long and unnecessary.
Describe alternatives you've considered
Previous to this, users will be notified of the process occurring (issue #921)
The text was updated successfully, but these errors were encountered: