Any suggestions on a folder to use for things like the pre commit hook?
Also wondering if this commit should format the existing code since it is not currently.
cb3f76aa17
refines MODELS around cart functionality, moves all pricing into Sku model, adds CouponCode model
also, are we going to do PR squashes, or should i squash this myself before merge?
I vote squashes, that way we can get a little messy but just squash to merge.
I like the idea of sharing any hooks we recommend for devs to use in an appropriate folder.
Ya I agree, I was thinking that but wasn't sure the director structure to go with. So the pull…
cb3f76aa17
refines MODELS around cart functionality, moves all pricing into Sku model, adds CouponCode model
So cargo fmt --check works as expected and returns non-zero when code is not formatted correctly. It also work recursively through project directories. cargo fmt is using rustfmt and we can…
Or maybe not, regarding the commit hook. I will test that out tonight and see what happens.
For Visual Studio Code the rust-analyzer extension has a knob for
rustfmton save and on paste.
Yep, and installing the Rust meta…
We should probably also incorporate #6 as well. This way even if someone doesn't use a formatter in one of our soon to be recommended ways, the code all still ends up with the same style.
I can do both later today, but unfortunately the day job is calling. So if anyone wants to do it before then, please do.