Replies: 1 comment 2 replies
-
My understanding is that
You can then query it: mise config get _.coursier.scalafmt
# id = "org.scalameta:scalafmt-cli_2.13"
# install_args = "-r sonatype:snapshots --main org.scalafmt.cli.Cli"
# version = "3.7.17" See the end of this section: https://mise.jdx.dev/configuration.html#global-config-config-mise-config-toml
[_]
foo = "bar" Otherwise, if you validate the configuration you suggested against the schema, you should see this error: There is a tool called dasel that you can use to query dasel -r toml -w json -f mise.toml _.coursier.scalafmt
{
"id": "org.scalameta:scalafmt-cli_2.13",
"install_args": "-r sonatype:snapshots --main org.scalafmt.cli.Cli",
"version": "3.7.17"
} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I found it very useful to put arbitrary configuration into
mise.toml
. For example I am installing a bunch of packages usingcoursier
(a scala package manager) andrebar
(an erlang package manager). Here is how I abusemise.toml
to specify which things to install.Then I can easily query the settings.
The reason it works because https://github.com/jdx/mise/blob/735cb3ee2601e203759cedd43df615a85bc4692b/schema/mise.json#L1504C1-L1506C6
The only downsides to this abuse are:
My proposal is to make extra configuration support official and disable warning by adding a setting:
The feature to list the keys on the selected level would be nice as well. Here is hypothetical use case.
This would simplify the commands I use
Beta Was this translation helpful? Give feedback.
All reactions