Skip to content
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

Add the ability to not remap unit files #54

Conversation

jerrymarino
Copy link
Contributor

I'd like to have the ability to copy unit files without
remapping them. For this PR #53
we still need to read in the unit files but not mutate the material.
This PR just removes the requirement on "remap" arg.

I'd like to have the ability to copy unit files without
remapping them. For this PR MobileNativeFoundation#53
we still need to read in the unit files but not mutate the material.
This PR just removes the requirement on "remap" arg.
@jerrymarino
Copy link
Contributor Author

cc @brentleyjones

Copy link
Contributor

@brentleyjones brentleyjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm

@keith ?

jerrymarino added a commit to bazel-ios/rules_swift that referenced this pull request Feb 22, 2021
@keith
Copy link
Member

keith commented Feb 22, 2021

in this case wouldn't you be better off just calling cp? i guess maybe the logic around not overwriting

also you'll have to sign the cla

@jerrymarino
Copy link
Contributor Author

@keith you could potentially just call ditto on the index to copy a subset into the target index, but in #53 it needs to serialize in the unit file to the copy the dependent files ( records in the case of #53 )

Cool, let me check this CLA I had issues sorting out out on my other PR!

@brentleyjones
Copy link
Contributor

@jerrymarino Thinking about this more, this change only really makes sense once we have something like #53. Can this just be part of that PR instead?

jerrymarino added a commit to bazel-ios/rules_swift that referenced this pull request Feb 23, 2021
@jerrymarino
Copy link
Contributor Author

@brentleyjones sure, I can add it to #53 - is this something that you think fits into this repo? I'd like to use the codepath I added there in Bazel and think this repo makes a nice "Swiss army knife" for indexes!

@brentleyjones
Copy link
Contributor

I think so, yes.

jerrymarino added a commit to bazel-ios/rules_swift that referenced this pull request Feb 25, 2021
@jerrymarino
Copy link
Contributor Author

@brentleyjones thanks for getting this in 👍

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.

3 participants