Repository navigation
Replies: 2 comments 2 replies
|
I like this proposal and the usability of the mocked search page. Just as a reference, in the Quarkus project, they are marking "build time options" with a lock 🔒 : |
2 replies
|
Search page is real, but I changed the label names for the above screenshot though: We're also already marking build options with the lock, that's already merged. |
|
Actually, changing the icon to a tool icon, as I think that represents "build" better than a lock: |
|
I also like the proposal. One could maybe add then when referring to a specific parameter, the terms |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We don't currently have strict/common terms to refer to build vs runtime configuration, and need to define some common terminology here as it would not be ideal if one guide refers to "options limited to build-time" while another guide calls it "build option".
The proposal here is:
Most people will expect that configuration can be done at runtime, without doing a build first, so using this terminology uses the standard term for configuration, while a separate term for special configuration that requires a build.
An example of using these terms in a sentence:
To configure the database first you need to select the vendor with the --db build option. Then you need to configure the URL with the db-url configuration option.
An example of using these terms on the options search page:
All reactions