[Project] Add method to stabilize UUIDs #283
Conversation
segiddins
force-pushed
the
seg-predictable-uuids
branch
from
ce9bec7 to
7f39e20
Compare
|
\c @alloy @kylef @orta @neonichu @mrackwitz I know the diff is small, and it needs some more tests, but I think it works. |
|
cool! |
|
Awesome! Yeah I'd like to see some tests for various types of objects. The doc should also state that it changes the uuids of objects and thus the user should not depend on being able to find them by uuid afterwards. |
|
Awesome 🎉 |
|
Hi, I'm sorry to intrude, just wanted to mention that original Xcode And a question regarding your logic of UUID generation: if I have two references pointing to the same file in the project, does it mean the generated UUID will be the same for both of them? |
|
@zats the issue with Xcode's UUID generation is that it's meant to be unique -- it includes a time stamp component. As to your question, they shouldn't be -- thanks to the distinction between PBXFileReferences and PBXBuildFiles, this should be fine. |
|
oh I see, thanks for the explanation! |
segiddins
force-pushed
the
seg-predictable-uuids
branch
2 times, most recently
from
85ed1eb to
70e9365
Compare
| @@ -409,6 +410,12 @@ def uuids | |||
| objects_by_uuid.keys | |||
| end | |||
|
|
|||
| # @note this should only be used for entirely machine-generated projects | |||
| # | |||
| def predictabilize_uuids | |||
There was a problem hiding this comment.
Is there a counter-part PR using this in CocoaPods?
There was a problem hiding this comment.
… script build phases
Also makes paths slightly more pleasant strings
segiddins
force-pushed
the
seg-predictable-uuids
branch
from
70e9365 to
44ec7bc
Compare
segiddins
force-pushed
the
seg-predictable-uuids
branch
from
44ec7bc to
010224e
Compare
[Project] Add method to stabilize UUIDs
|
I think I'm experiencing an issue with deterministic UUIDs here, do you have an idea what might be wrong here @segiddins ? |
Closes #175