refactor(build): use immutable functions for retrieving compile-time variables#84
Merged
water-sucks merged 1 commit intonix-community:mainfrom Jul 7, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
-ldflagsoption forgo builddoes not support setting types other than strings for variables.As such, for the
buildOpts.Flakecompile-time variable, this resulted in unwieldy string comparisons everywhere to determine Boolean values.This fixes that DX issue by exposing functions that return the values for each compile-time variable in the
internal/buildpackage, and the variables themselves are moved to separateinternal/build/varssubpackage that should not be touched by anything other than the Go build system.