JSON, TOML & YAML support

[PurpleBooth]

Along side regex it would be really powerful to be able to specify a path to update in JSON or TOML or YAML

  - 
    file: ./package.json
    json: 'version'
  - 
    file: ./package.json
    json: 'some-key.something.version'

It sort of sucked writing a regex to update my package JSON (not un-doable, just a bit of a faff). Most languages use one of those 3 file formats for their package details file, so it might be worth making it easier to bump with that.

[ga-paul-t]

Hi @PurpleBooth thanks for raising this discussion. I agree that regex can be a pain to write. I have quite a few ideas that I want to implement in this area of uplift to improve the whole file bumping concept. I really like this suggestion!

I have been toying with the idea of having uplift auto-detect common files and bump them automatically without the need to provide configuration. But this feels like a good natural first step

[ga-paul-t]

I'll raise some issues in the coming days to capture these approaches. I will look at JSON paths first, then YAML and TOML. I will have a look around and see if there are some good quality libraries that I can make use of

[ga-paul-t]

Raised the first issue to support the inclusion of JSON paths: #89

From the back of this ticket, I will look into YAML and TOML files

[PurpleBooth]

Cool! I am enjoying using the tool at the moment, it was easy to setup, and felt intuitive to use, so nice work!

[PurpleBooth]

Ohh, exciting!

[ga-paul-t]

uplift now supports basic JSON path file bumping

[PurpleBooth]

I will give it a go this evening 😄

Thanks for adding this!

[PurpleBooth]

I gave it a go and it was super easy and intuitive! Thanks!

[ga-paul-t]

@PurpleBooth I have been looking into lots of different go libraries for setting values within TOML, JSON, and YAML files, but they all seem to have the same underlying issue. Go typically supports a map with no concept of ordering. So if you dynamically load a file into a map, set a value with a path, and then write it back to the file, it will typically be in random order.

Do you know if Rust suffers from the same issue? Do you have much experience with serialisation in Rust?