-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[core-api][experimental] Definitions.merge
#26704
base: 12-23-_core-api_experimental_create_repository_using_definitions_args_
Are you sure you want to change the base?
[core-api][experimental] Definitions.merge
#26704
Conversation
94f89e3
to
25d1bd6
Compare
042185a
to
d096946
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving for the decision, but i think docs is pretty important for this one.
This one I am not totally sold on yet since components might in fact hide this forever since it called on the user's behalf. |
25d1bd6
to
632d3a9
Compare
d096946
to
beab8e1
Compare
632d3a9
to
b534d44
Compare
beab8e1
to
490e571
Compare
b534d44
to
7bec214
Compare
490e571
to
ff38870
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to discuss this one as I'm not sure we want to support it forever with components coming
Summary & Motivation
decision: experimental -> GA
reason: we are leaning heavily on this behavior in components-land, and generally see this as a good tool when organizing a code location. we should formally endorse it
docs exist: no (will likely need to create some sort of guide along the lines of "organizing code locations", which would reference this)
How I Tested These Changes
Changelog