Feature Request : simplify use of variables and profiles about toml-bombadil HOT 2 CLOSED

The problem with this approach is that representing config like this is not straight forward :

[[dot]]
# ... 

# Dot for corporate profile
[[dot.corporate]]
# ...

[[dot]] represent an entry in a Vec<Dot> and [[dot.corporate]] would be deserialized as HasMap<String, Dot> we could use the toml crate to handle deserialization manually.

An alternative representation would be to add dots, hooks and vars entries under a nested Profile struct this would look like this :

# This is the default profile
[dots]
maven = { source = "maven/settings.xml", target = ".m2/settings.xml" }
alacritty = { source = "alacritty/settings.xml", target = ".config/alacritty" }
vars = [ "colors.toml", "env.toml"]
hooks = [ "sway reload", "echo 42"]

# This how we would add profile, no need to repeat inner values that are not overwritten (such as dot.target)
[dots.profiles.corporate]
maven = { source = "maven/settings.corporate.xml" }
vars = [ "colors.toml" ]
hooks = [ "echo \"evil corp \"" ]

Intermediate json representation would be this :

{
  "dots": {
    "hooks": [
      "sway reload",
      "echo 42"
    ],
    "vars": [
      "colors.toml",
      "env.toml"
    ],
    "alacritty": {
      "source": "alacritty/settings.xml",
      "target": ".config/alacritty"
    },
    "maven": {
      "source": "maven/settings.xml",
      "target": ".m2/settings.xml"
    },
    "profiles": {
      "corporate": {
        "hooks": [
          "echo \"evil corp \""
        ],
        "vars": [
          "colors.toml"
        ],
        "maven": {
          "source": "maven/settings.corporate.xml"
        }
      }
    }
  }
} 

This is be less verbose but the trade-off would be that all dot entry needs to be named. Overriding profile value would be easier to implement since we just need to match [dots.name] against the default profile.

from toml-bombadil.

closed by #29 and #28

from toml-bombadil.