Scope extensions update to split "origin" and "site" type extensions #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Incomplete changes to scope_extensions-explainer.md
…lainer, leaving "site" extensions to be addressed by a seperate explainer
|
I expect to add a "Alternatives considered" section at a later time from summaries of past design discussions. The current PR contains the bulk of the update we need to fully represent the simple "origin" type extensions. |
LuHuangMSFT
added
the
scope-extensions
|
@diekus, @HowardWolosky PTAL. |
dmurph
requested changes
Oct 24, 2024
HowardWolosky
approved these changes
Oct 26, 2024
jahn00
reviewed
Oct 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to split the current explainer into 2 parts. The first covers "origin" type extensions and all the additional information (association file, etc) needed for that. The 2nd part will propose the "site" type extensions and the additional security measures needed to enable that.
This PR edits the existing explainer to cover the first part.