-
Notifications
You must be signed in to change notification settings - Fork 45
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
[Bug] Fixes spaces in variable resolution for base parser #68
[Bug] Fixes spaces in variable resolution for base parser #68
Conversation
line = "Hello $ (name)!" | ||
self.assertEqual(parser.ReplaceVariables(line), "Hello sean!") | ||
line = "Hello $( name )!" | ||
self.assertEqual(parser.ReplaceVariables(line), "Hello sean!") |
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.
Can you add a test for the negative case? e.g. missing $
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.
like line = "Hello name"
or line = "Hello $name"
?
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.
First one, then the other! :)
Is this syntax valid according to DSC spec? Is it allowed 1 space? N spaces? |
@spbrogan according to the spec here, no. https://edk2-docs.gitbooks.io/edk-ii-dsc-specification/content/v/release/1.28/3_edk_ii_dsc_file_format/33_platform_dsc_definition.html but then here: https://edk2-docs.gitbooks.io/edk-ii-dsc-specification/content/v/release/1.28/appendix_b_sample_edk_ii_dsc_file.html they use $ () in a few places. I say let's go with the spec on this one. |
fixes #56