-
Notifications
You must be signed in to change notification settings - Fork 129
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
Support for BuildInfo
#2106
Closed
Labels
enhancement
New feature or request
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Discussed in #2051
Originally posted by ckipp01 April 23, 2023
I have a use case where I'm building a CLI app. A lot of times with apps like this you want to make sure you can display the version of the app via a command, and many times the value of that version is persisted utilizing a form of
BuildInfo
where based on git, or something else a file is generated and used for compilation. Is there any way to mimic something like this withscala-cli
? All the solutions I'm coming up with request runningscala-cli
to generate a file first, and then running it again on your main project to utilize that created file. However, it'd be great if this could just be done in a single step somehow. Any ideas?Describe the solution you'd like
We could have a directive/command-line option exposing
BuildInfo
data in the project.//> using build.info
Describe alternatives you've considered
This could potentially also be delivered through code generators. (see #610)
Additional context
See the discussions in #2051 and #610.
The text was updated successfully, but these errors were encountered: