Skip to content
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

fix: ensure properties are correctly resolved #12

Merged
merged 2 commits into from
Sep 10, 2022
Merged

fix: ensure properties are correctly resolved #12

merged 2 commits into from
Sep 10, 2022

Conversation

ckipp01
Copy link
Owner

@ckipp01 ckipp01 commented Sep 10, 2022

Prior to this change only the maven properties were actually resolved
leaving the rest not. This would cause for example $package$ to end up
being generated as $package. Now we ensure everything that we can is
resolved by mimicking the way it's done in the sbt plugin.

NOTE: I still plan on improving this a bit by allowing the user to pass
in values to validate/generate which can be used to generate with
specific values.

Closes #11

Prior to this change only the maven properties were actually resolved
leaving the rest not. This would cause for example `$package$` to end up
being generated as `$package`. Now we ensure everything that we can is
resolved by mimicking the way it's done in the sbt plugin.

NOTE: I still plan on improving this a bit by allowing the user to pass
in values to validate/generate which can be used to generate with
specific values.

Closes #11
@ckipp01 ckipp01 merged commit fe1f0bf into main Sep 10, 2022
@ckipp01 ckipp01 deleted the properties branch September 10, 2022 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Properties are not resolved
1 participant