| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
Next to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Adds an explicit overrideAccess: true to every Local API call in packages/ that
previously relied on the default.
This is preparation for making overrideAccess a required property, which lands
later in 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 overrideAccess to true. Writing the value
explicitly produces exactly what the default already produced.
Every added line is identical — overrideAccess: true, — and nothing is removed.
The drizzle and db-mongodb sites are all migrations and data upgrades, which run
as the system with no user attached.
Note on the ui server functions
Four of the ui sites are server functions — views/List/handleServerFunction.tsx,
views/Document/handleServerFunction.tsx, getNavPrefs, and upsertPreferences.
Our own guidance says server functions should use overrideAccess: false and pass
user. They are set to true here because that is what the default already produced,
which keeps this PR a no-op. They are not newly unsafe, the queries are already scoped
by user.value equals user.id but switching them to false is a behavior change and I am trying to avoid those here.