Add ability to initialize scheme without a blueprint identifier

[daltonclaybrook]

Resolves #509

Short description 📝

This PR fixes an issue where some schemes cannot be deserialized because a buildable reference does not contain a blueprint identifier.

Solution 📦

The solution is to make the blueprint field optional on BuildableReference. The other option I considered was adding a new case to Blueprint called .none, but I felt simply making the property optional would be more ergonomic.

[daltonclaybrook]

Is anyone available to take a look at this? (cc: @pepibumur)

[kwridan]

Thanks for submitting this @daltonclaybrook

The changes look good, I have some small observations.

• swift package generate-xcodeproj does indeed generate schemes without the blueprint identifier, though Xcode overwrites those schemes to include them when viewing them in the scheme editor. At least with this change, those generated projects and schemes can be parsed correctly.
• This is a slightly breaking change and will need to mark it such in the CHANGELOG.md or perhaps it may need to be part of a major release - @pepibumur thoughts?
  • Example: XcodeGen relies on the public blueprintIdentifier change here

[daltonclaybrook]

Any action items on my end to get this moving? (cc: @kwridan @pepibumur)

[pepicrft]

Hey @daltonclaybrook 👋🏼
I propose that we update the CHANGELOG.md with your changes, and flag them as breaking. I'll release a major version of XcodeProj once this is merged.

[kwridan]

Thanks @pepibumur! will submit a fix for tuist/tuist#2991 first thing tomorrow as it's similar in breaking nature which can be bundled in the same major release.

[kwridan]

@daltonclaybrook mind rebase / merging latest main with an updated change log?

[daltonclaybrook]

@kwridan yep, I'll be able to take care of that later this morning.