chore: make overrideAccess explicit in examples - #17865
Merged
Merged
Conversation
nathanlentz
marked this pull request as ready for review
August 20, 2026 13:31
nathanlentz
force-pushed
the
override-access/examples
branch
from
August 20, 2026 13:31
256d48e to
7a88fbe
Compare
nathanlentz
requested review from
AlessioGr,
JarrodMFlesch,
denolfe and
jacobsfletch
as code owners
August 20, 2026 15:31
nathanlentz
force-pushed
the
override-access/examples
branch
from
August 20, 2026 15:31
7a88fbe to
36b1352
Compare
nathanlentz
force-pushed
the
override-access/examples
branch
from
August 20, 2026 16:42
36b1352 to
35a3965
Compare
nathanlentz
force-pushed
the
override-access/examples
branch
from
August 21, 2026 17:34
35a3965 to
662fadc
Compare
nathanlentz
force-pushed
the
override-access/examples
branch
from
September 8, 2026 14:07
662fadc to
1c18edd
Compare
Base automatically changed from
override-access/templates
to
override-access/packages
September 23, 2026 20:05
nathanlentz
added a commit
that referenced
this pull request
Sep 23, 2026
## Summary Make `overrideAccess: true` explicit in Local API calls across first-party packages, plugins, templates, and examples. These calls currently rely on a default of `true`, so their behavior stays the same. This prepares them for the default change in #17869. ## Scope Calls that intentionally exercise the default remain unchanged. Template calls keep their current access behavior; changes to template access decisions need separate review. The test call sites were addressed in #17859, which is already merged. This PR combines #17862, #17864, and #17865 into #17861. ## Validation The branches merged without conflicts. `git diff --check` passes for the combined change. CI will validate the consolidated branch.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds an explicit
overrideAccess: trueto every Local API call inexamples/thatpreviously relied on the default.
This is preparation for flipping the Local API default to
false, which lands laterin this stack. It is split out so that the breaking change itself stays small enough
to read.
This changes no behaviour
The Local API currently defaults
overrideAccesstotrue. Writing the value explicitlyproduces exactly what the default already produced.
localizationmulti-tenantlive-previewremix,form-builder,draft-preview,auth,astrocustom-componentsVerification
Examples are standalone projects with no dependencies installed, so they cannot be
typechecked.