-
Notifications
You must be signed in to change notification settings - Fork 41
Add fix to return enum string values #800
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
@mgreenegit I'm bothering Steve too much, so I thought of giving you a heads-up. Could you take a quick look at this one? It shouldn't be that big of a change. |
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.
Minor nits for readability and spacing characters.
Thanks @michaeltlombardi for the check. I thought there was a remark once to do it in the style Pester tests are written (OTBS). I switched the blocks in |
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
PR Summary
This PR addresses #791. While it is a small redesign, casting the value to a string makes logical sense. When users are exporting or getting values, they can capture the results and store them as a configuration document instead of having them returned as integers. This would match the schematics, even though that is not implemented fully.