We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do parameters support spaces around the =? parameter "foo"="bar" parameter "bar" = "foo"
parameter "foo"="bar"
parameter "bar" = "foo"
The developer documentation uses both. Is one more "safe" than the other? Is one "will work" and the other "probably works"?
Parameters are supported inside prefetch blocks. Does this use change the guidance on spaces? Does indenting of lines impact the results?
Note these relevant forum threads: https://forum.bigfix.com/t/whats-wrong-with-this-statement/16489 https://forum.bigfix.com/t/weird-issue-with-whitespace-in-actionscript-or-site-permissions/48141/1
(This customer site has used spaces in parameters since always, seemingly without negative impact.)
The text was updated successfully, but these errors were encountered:
Do parameters support spaces around the =?
Yes.
No, simply the grammar for the parameter commend allows whitespace between the parameter name/value and the = sign.
parameter
=
Sorry, something went wrong.
No branches or pull requests
Do parameters support spaces around the =?
parameter "foo"="bar"
parameter "bar" = "foo"
The developer documentation uses both. Is one more "safe" than the other? Is one "will work" and the other "probably works"?
Parameters are supported inside prefetch blocks. Does this use change the guidance on spaces? Does indenting of lines impact the results?
Note these relevant forum threads:
https://forum.bigfix.com/t/whats-wrong-with-this-statement/16489
https://forum.bigfix.com/t/weird-issue-with-whitespace-in-actionscript-or-site-permissions/48141/1
(This customer site has used spaces in parameters since always, seemingly without negative impact.)
The text was updated successfully, but these errors were encountered: