Closed stuartlynn closed 1 year ago
I think we could take this in a couple of steps, but I think comittizen is something we could eventually get in. I'll break this task down on Friday.
I'll try to approach this in a couple of distinct PRs so that all changes are isolated:
This pathway obviously relies on Prettier being able to run on Rust, which it should, but should that not be the case I'll add 2 PRs for installing the Rust Prettier equivalent and then running it on the Rust code base.
Sounds good to me. If prettier can't do rust well enough we should be able to just use "cargo fmt" which comes as standard with cargo the rust package manager.
Just a quick note to say because we have this setup as a monorepo, you prob want to install all of this at the root level, ie in the package.json in the root directory.
Yup, the root level is where I'm installing it! Given that I went with Google's TypeScript formatter, I think I'll be using cargo fmt
.
With the merging of https://github.com/Matico-Platform/matico/pull/222, this PR is done.
What I have used in the past which has worked pretty well is
While we are thinking about dev tooling as well, it might be worth considering using something akin to comittizen to standardize commit messages and make it easier to produce release notes in future.