Jörn Berkefeld
Jörn Berkefeld
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior ![image](https://github.com/Accenture/sfmc-devtools/assets/1917227/b96e5c38-bdf4-4bcd-9385-b5f78a389b9f) ### Expected Behavior should simply show an error and exit...
--> users can update the patch versions of their client without impact --> as soon as the project's config file's version was increased (even if it's just the patch) then...
right now, if variables were found in the template but not in the market, the variables are stripped from the template and the files are saved without {{{...}}} - as...
![image](https://github.com/Accenture/sfmc-devtools/assets/1917227/abb42dcd-dc34-44cd-9a7a-a81b80470ac8)
![image](https://github.com/Accenture/sfmc-devtools/assets/1917227/e3b0889b-eca1-43eb-bea0-9d1748e55c47)
![image](https://github.com/Accenture/sfmc-devtools/assets/1917227/67ef2fa7-8814-497e-9c30-e50f7a18caef)
relevant for API endpoints that fail if we send the wrong fields, including upper/lowercasing maybe like this? https://stackoverflow.com/a/60153314
- [ ] old JSON is deleted - [ ] new JSON is created - [ ] extracted files are also renamed (deleted + created)
% Stmts | % Branch | % Funcs | % Lines ---------|----------|---------|--------- 75.57 | 55.33 | 84.21 | 75.52