-
Notifications
You must be signed in to change notification settings - Fork 267
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
Resolves #888: New optional parameter to SetMojo: interpolateProperties #889
Resolves #888: New optional parameter to SetMojo: interpolateProperties #889
Conversation
…Properties - allows to disable property interpolation, so that it's possible to match against raw property values as well as replace properties with interpolated values if the value is the same as the property value
@slawekjaranowski lots of new PRs, here's one more :) |
…nsMojo and UseNextReleasesMojo in case of no newer versions/releases
…nsMojo and UseNextReleasesMojo in case of no newer versions/releases
@slawekjaranowski why did you close this PR? |
Commit with closing keyword was pushed to master. |
Please reopen. Wrong commit message on that other PR. :| |
The commit message was ok: there is both an issue 889 as well as a PR 889.... |
Is that possible? |
So indeed wrong commit message. |
Was classed because was mentioned in merged PR
|
Should I create a new one? |
Reopened 😄 |
This is my take on resolving the problem which occurs when the user wants to match against a version which is the same as the interpolated property value. If this is the case, by default, the file is left unchanged, so that it continues to contain the properties.
If the new parameter is employed, it is possible to disable interpolation for such cases, but one needs to match against the raw value (e.g. use the property name, or
*
), and the value will be replaced.