fix(gradle): when multiple gradle operations on the same file, only t…

[ngandon]

When multiple operation on the same gradle file, fix the issue where only the first operation was taken into account

#182

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
trapeze	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 25, 2023 0:06am

[Crylion]

Can you elaborate on what this fixes for you?
If I understand your changes correctly, it basically reuses the fetched gradle file for later entries instead of fetching it again for every instruction, but the end result should be the same. For each entry, the gradle file gets fetched, and the instruction is processed. With your code it is definitely more efficient, but otherwise the functionality stays the same, no?

[ngandon]

Hello @Crylion,

Indeed it seems like the functionality would stay the same.
However, when fetching the gradle file for each entry, only the first update was registered in the end. I didn't check exactly why, but fetching the gradle multiple time was overwriting the changes.

And thanks for the merge

[mlynch]

This is live in @trapezedev/configure@next, mind testing it @ngandon and make sure it's working for your needs? Thanks for the PR!