Swift Evolution Metadata Proposed Changes

It’s awesome to see this discussion about something I’ve been looking at for a while when building Proposal Monitor, the app I just announced on Community Showcase. Recently I’ve noticed a few meaningful changes that had impact in the app and agreeing on a schema is the best way to avoid those problems.

I believe the proposed schema is great and improves a lot over the original.

Nonetheless, I’d like to know more about the title and summary fields. Today they contain the markdown version of their contents. Are they going to keep being like this? Should we formalize this somewhere? (Considering my use case I prefer it to keep storing the markdown content)

And I’m not sure if this question fits here, but I’d like to know if changes to the summary parsing could be discussed as some proposals simply have no summary as of now (SE-0425 is an example).

1 Like