When I ran taze after creating a pnpm-workspace.yaml file to use a catalog, taze stripped all the comments out of the yaml file.
When I said yes to "write to package.json", taze also re-wrote my pnpm-workspace.yaml file, normalizing the quoting of values - but also stripping out all the comments. There were no version changes made to anything in the catalog, so the workspace file didn't need to be touched at all.
Please don't strip out the comments - they're one of the best features of using yaml files for this, allowing me to document why I'm making these version choices, the purpose of the catalogs, etc...
Describe the bug
When I ran taze after creating a pnpm-workspace.yaml file to use a catalog, taze stripped all the comments out of the yaml file.
When I said yes to "write to package.json", taze also re-wrote my pnpm-workspace.yaml file, normalizing the quoting of values - but also stripping out all the comments. There were no version changes made to anything in the catalog, so the workspace file didn't need to be touched at all.
Please don't strip out the comments - they're one of the best features of using yaml files for this, allowing me to document why I'm making these version choices, the purpose of the catalogs, etc...
Reproduction
https://github.com/dflock/taze-bug-repo
System Info
Used Package Manager
pnpm
Validations
Contributions