Avoid whitespace changes for arrays in automatic config migrations #30786
-
What would you like help with?I would like help with my configuration How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.GitLab Please tell us more about your question or problemI recently got a config migration PR from Renovate, which was correctly migrating some fields. However, it added whitespaces to all of my arrays. Example:
As seen in this example, I found this Issue where @rarkins explained the same problem. There seems to be a solution with prettier but I can't really get my head around that. When I run the validator locally, it doesn't shatter the JSON and when I run format on the file in VS Code it also doesn't change something. Can someone point me in the right direction? Logs (if relevant)No response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
We want to make "getting config migration PRs from Renovate" the default behavior in a new major version (see #16359). But before we can make it the default, we need to stop/reduce the amount of whitespace changes. I think this issue is most relevant here, as that is about using a different JSON parser, which may do better with whitespace changes? |
Beta Was this translation helpful? Give feedback.
We want to make "getting config migration PRs from Renovate" the default behavior in a new major version (see #16359). But before we can make it the default, we need to stop/reduce the amount of whitespace changes.
I think this issue is most relevant here, as that is about using a different JSON parser, which may do better with whitespace changes?