Split components between destructiveChangesPre.xml and destructiveChangesPost.xml

[yaniv3109]

Is your proposal related to a problem?

---

Further to our correspondence, I am creating a case at your request.
After running the comparison command, 2 main files are created: package and destructiveChanges
I wanted to ask about a case where some component was deleted. How should I know if in the deploy command I should use destructiveChangesPost.xml or destructiveChangesPre.xml.
I understand the idea that if it is about dependencies or impact on other components but how can this be done automatically?

what do you think about that?

[scolladon]

Hi @yaniv3109 !

Thanks for raising this issue and thanks for contributing in making this project better!

I actually do not have a strong opinion about that
I think it is hard to define rules that are true for every one about where to list component to destruct.
If we can come with some patterns then we could implement that

[yaniv3109]

Totally agree and by default (at least in my case) I used pre. ‫בתאריך יום ה׳, 26 בספט׳ 2024 ב-18:54 מאת ‪Sebastien‬‏ <‪ ***@***.***‬‏>:‬

…

Hi @yaniv3109 <https://github.com/yaniv3109> ! Thanks for raising this issue and thanks for contributing in making this project better! I actually do not have a strong opinion about that I think it is hard to define rules that are true for every one about where to list component to destruct. If we can come with some patterns then we could implement that — Reply to this email directly, view it on GitHub <#923 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BB2WMRMQAIU5NOJOHIJWFL3ZYQU3HAVCNFSM6AAAAABO5HKVUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGM2TGNBWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>