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

Adopt new Swift Evolution metadata file format #4

Merged
merged 5 commits into from
May 21, 2024
Merged

Adopt new Swift Evolution metadata file format #4

merged 5 commits into from
May 21, 2024

Conversation

ole
Copy link
Collaborator

@ole ole commented May 14, 2024

This change adapts to schema version 1.0.0 of the Swift Evolution metadata file format, which went live on 2024-04-21 (with schema version "0.1.0" during the transition). For more info on the changes in the new schema, see James Dempsey’s posts at https://forums.swift.org/t/swift-evolution-metadata-transition/71387 and https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.

The old schema will stop working on 2024-07-22, so we need to ship an update before then.

Fixes #2.

ole added 4 commits May 14, 2024 19:51
This adds a new `make dev` command that builds a version of the Alfred workflow with a different name and bundle ID. This is useful for testing the workflow in Alfred during development without overwriting the production version.
This change adapts to schema version 1.0.0 of the Swift Evolution metadata file format, which went live on 2024-04-21 (with schema version "0.1.0" during the transition). For more info on the changes in the new schema, see James Dempsey’s posts at https://forums.swift.org/t/swift-evolution-metadata-transition/71387 and https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.

The old schema will stop working on 2024-07-22, so we need to ship an update before then.

Fixes #2.
We had previously repeated the proposal title in the subtitle because the title field might get truncated earlier due to its bigger font size. However, now that we display some additional metadata in the subtitle (version when a proposal was implemented, review period of proposals in review), I think not repeating the title is better.
@ole ole changed the title Adopt new Swift Evolution metadata file formatNew schema Adopt new Swift Evolution metadata file format May 14, 2024
@ole
Copy link
Collaborator Author

ole commented May 14, 2024

Nice benefit of the new file format: we can display additional metadata. Note the Swift versions for "Implemented" proposals and the dates of the review periods for "Active Review" proposals.

2024-05-14-Alfred-Swift-Evolution

@ole
Copy link
Collaborator Author

ole commented May 14, 2024

I'd like to ship a new version fairly soon to give people enough time to update before the old file format stops working, but I'd really love to add one more feature, and that is local caching of the JSON file: see #5.

@ole
Copy link
Collaborator Author

ole commented May 15, 2024

I chose this wording for listing upcoming feature flags in the subtitle: "Feature flag: GlobalConcurrency (enabled in Swift 6 language version)"

The downside is that it's fairly long and may get truncated depending on how big your Alfred window is? I couldn't come up with a shorter text that I found was equally clear. I'm very open to suggestions.

2024-05-15-Alfred-Swift-Evolution-feature-flag-2

Base automatically changed from make-dev to master May 16, 2024 19:36
@ole ole merged commit e9935ce into master May 21, 2024
@ole ole deleted the new-schema branch May 21, 2024 15:52
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.

Adopt upcoming Swift Evolution metadata file changes
1 participant