-
Notifications
You must be signed in to change notification settings - Fork 563
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
[Site] Schema needs to be updated on the site #4879
Comments
please review this issue for target Milestone, Inconsistencies & Priority upon triage. |
Hi @paulcam206. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions. |
@matthidinger / @dclaux / @shalinijoshi19 FYI |
@RebeccaAnne ? I dont think we got traction on this from Paul's end before he left on leave. Can you pick it up to determine when/how this will need to be fixed - time for 20.10? |
@shalinijoshi19 This tracks the larger conversation around how we want to handle versioning our schema. #4884 is the immediate issue of updating our current schema to the latest version. I've moved that one back into 20.10, but this one represents a longer term conversation. |
Although we've updated the current schema to the 1.3.0 version of the schema with #4884, this issue tracks whether we wish to revisit how we handle schema versioning.
Looks like this will require a bit more planning -- specifically, the currently published schema is our 1.3.0 schema. Should newer schemas are published at versioned URLs (e.g. https://adaptivecards.io/schemas/1.4.0/adaptive-card.json). We need to square our structure with our card author guidance. Should the unversioned URL be considered "latest", or should it be the 1.3 schema encased in amber?
Some points:
"isRequired": "steve"
weren't flagged for an invalid type when we we on the 1.1 schema)$schema
The text was updated successfully, but these errors were encountered: