Skip to content

Conversation

@Rockdell
Copy link
Contributor

This PR aims to fix issue #512.

When using dynamic replacement with multiples files being processed, the replacement value was being overridden after the first processed file.
This fix separates the dynamic processing replacement from the standard replacement string as to not lose its value when parsing multiple files with the replacement-js flag.

Two testing scenarios were added to test these instances.

@mathiasrw
Copy link
Owner

Thank you!

@mathiasrw mathiasrw merged commit 73fe5f7 into mathiasrw:main Sep 11, 2024
@mathiasrw
Copy link
Owner

The CICD worked smoothly, but I’m getting an error in my local setup, which is odd. I’ll need to investigate why this is happening.

I’ll publish a new version as soon as possible, but I’ll probably only have time to look into it over the weekend.

@mathiasrw
Copy link
Owner

mathiasrw commented Sep 13, 2024

Turns out with async read + transformation of files you can't predict the order of output. Complexity does really grow exponentially.

🎉 Things got sorted and your awesome contribution is out in the wild now as part of v7.1.11 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants