Potential fix for bug #5145 to suppress any errors #5146
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e is already activated
|
Hey @reshmee011 - I think we should just update the documentation and mark the parameter obsolete for this since we are not using it anywhere in the code. |
|
It feels like the right action to mark the parameter as obsolete. I will do that, thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for bug #5145 to suppress any errors if -force parameter is specified.
Type
Related Issues?
Fixes #5145
What is in this Pull Request ?
Currently the force parameter is not being used in the codebase. Updating the EnableFeature.cs to have error handling and throw exception message on error only if Force parameter is not specified.