-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
om init
does not replace strings under matching directory name
#425
Comments
om init
does not replace strings under maching directory name
An one-liner repro command is useful for bug reports like this. IIUC: Current behaviour
Expected behaviourAll those |
With #435 ![]()
![]() |
@cameronraysmith Thanks for these bug reports. We are planning to make a release of omnix next (all the way to |
om init
does not replace strings under maching directory nameom init
does not replace strings under matching directory name
You covered everything I encountered except for the one you already identified in #428 . |
I am not certain the issue title captures the correct condition, but I have noticed in https://github.com/sciexp/python-nix-template/blob/7d17d0dbffe756f1804aa86fe95bf61a1867d4d3/nix/modules/template.nix that when I create new template instances, a directory name that matches a string replacement rule is correctly renamed but all the files below it fail to receive that same string replacement.
See the timestamps in the description of https://asciinema.org/a/WkHfv6v6vd5qUNlCVbbKzbKcp
for an example of this.
In particular the directory here gets replaced as expected
https://github.com/sciexp/python-nix-template/tree/7d17d0dbffe756f1804aa86fe95bf61a1867d4d3/src/python_nix_template
but instances of the same matching string do not get replaced in any of the files within that folder, such as this particular example
https://github.com/sciexp/python-nix-template/blob/7d17d0dbffe756f1804aa86fe95bf61a1867d4d3/src/python_nix_template/tests/test_main.py#L5
example template output
It's also certainly possible I've misinterpreted the nature and cause of this issue since I haven't reviewed the omnix source.
The text was updated successfully, but these errors were encountered: