Update description for outputFileName parameter in Customizations #116
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
This change will provide users with more clarity on how the outputFileName parameter works, making the tool easier to use and understand. It took me a lot of digging to understand that changing the extension for the `outputFileName` resulted in a different format for the output of the file. This will clarify it for future folks
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.
This change will provide users with more clarity on how the
outputFileNameparameter works, making the tool easier to use and understand.It took me a lot of digging to understand that changing the extension for the
outputFileNameresulted in a different format for the output of the file. This will clarify it for future folks