As it stands, trying to add anything to this PAC in a consistent way is near impossible.
On a clean checkout, if I run cargo run -p generator -- generate (like CI does) I end up with a ton of modified files.
On any file removal/rename (say, chiptool changing case on output) git add will keep all the old files as well as the newly generated files.
If I attempt to remove the already generated files, generator fails because nxp-pac is part of the workspace, but the workspace is now not buildable.
I don't know how you've enforced consistency so far, but I think this current strategy doesn't scale well beyond 1 developer. It doesn't give me much confidence that anything I'm adding is being correctly auto-generated.
I would write some automation myself, but since it's not really documented how it's expected for this repo to be updated it's kinda hard to even know where to start...
As it stands, trying to add anything to this PAC in a consistent way is near impossible.
On a clean checkout, if I run
cargo run -p generator -- generate(like CI does) I end up with a ton of modified files.On any file removal/rename (say, chiptool changing case on output)
git addwill keep all the old files as well as the newly generated files.If I attempt to remove the already generated files, generator fails because nxp-pac is part of the workspace, but the workspace is now not buildable.
I don't know how you've enforced consistency so far, but I think this current strategy doesn't scale well beyond 1 developer. It doesn't give me much confidence that anything I'm adding is being correctly auto-generated.
I would write some automation myself, but since it's not really documented how it's expected for this repo to be updated it's kinda hard to even know where to start...