Closed dempseyatgithub closed 6 months ago
Note that there are now proposals implemented in Swift 6.0 with upcoming feature flags that are only valid in Swift 6.0 under the Swift 5 Language Mode. Over the course of Swift 6.x releases some UFFs will be valid only in Swift 5 Language Mode, some valid only in Swift 6 Language Mode.
The header field in each proposal may need to include the valid language mode which would need to be represented in the metadata.
Based on feedback from the Language Steering Group, this field would most likely be a JSON object containing the flag and a second field with the language mode version where the flag is superfluous because the feature is always enabled.
Add field as described in the metadata change proposal https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779
Resolved by 44c5ad305e3486fa5920740aa932eea79546d703.
Currently, the SE Dashboard script keeps a manual mapping of proposal ids to upcoming feature flags.
This value, if present, should be included in the metadata for that proposal.
Because this is not a common field, it will be an optional field in the proposal metadata.
Adding it will allow the SE Dashboard to automatically report upcoming feature flags without manual updating.