storedbox / cargo-yaml Goto Github PK

• the -c and --color cmdline flags should not be ignored
• when color is enabled, output should mirror the coloring scheme of builtin Cargo subcommands
• when color is set to auto, color should be enabled on (color) terminals and disabled otherwise

@storedbox

it looks like this repo doesn't see much action and issues don't seem to get replied to. I'm using cargo yaml every day, and I wouldn't mind maintaining it.

please get in touch!

currently writing

package:
  edition: 2018

throws an error because in the toml file it must be a string.

I like cargo-yaml, but obviously I'm going to forget calling it before issuing cargo commands. Some security is in order here. I wondered about watching Cargo.yml for changes, but watching is always quite a pain. I found a solution for my personal case, so I though I share it here. Maybe it's good enough to be included in the readme, but since I use fish shell, it's not bash...

I put the following in my config.fish

function cargo --wraps=cargo --description="Wraps cargo to make sure cargo-yaml is called if Cargo.yml has changed"

	if         test   -e Cargo.yml                               # if Cargo.yml exists
	if command test ! -e Cargo.toml -o Cargo.yml -nt Cargo.toml  # and it's newer than Cargo.toml

		command cargo yaml                                        # run cargo-yaml

	end
	end

	command cargo $argv                                          # call actual cargo command passing arguments

end