-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: payloadcms/payload
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.0.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: payloadcms/payload
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.0.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 12 commits
- 137 files changed
- 7 contributors
Commits on Nov 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1dc8094 - Browse repository at this point
Copy the full SHA 1dc8094View commit details -
docs: update what-is-payload.mdx (#9353)
### What? instead of saying "it", wanted to give more context to what goes into your Next app folder. ### Why? clarification ### How? edited docs
Configuration menu - View commit details
-
Copy full SHA for 646a534 - Browse repository at this point
Copy the full SHA 646a534View commit details -
fix: allow self referencing relationships when adding new collections…
… to config (#9360) ### What? Unable to add collections to the config dynamically if they reference their own collection in a relationship field. This was discovered while working on the folder view feature which dynamically adds collections to your config if it is enabled per collection. ### Why? When `sanitizeCollection` runs, it takes the current config. If you are sanitizing a collection before adding it to the config, that collection cannot have any self referencing relationship fields on it otherwise it fails the validRelationships check. ### How? Using a reducer we now initialize the validRelationships variable with the incoming collection slug.
Configuration menu - View commit details
-
Copy full SHA for 4030e21 - Browse repository at this point
Copy the full SHA 4030e21View commit details
Commits on Nov 20, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9e85be0 - Browse repository at this point
Copy the full SHA 9e85be0View commit details -
docs: fix custom component links in admin (#9368)
### What? Fixes links for custom components in a few places in admin docs. ### Why? To link users to the correct location in the docs. ### How? Changes to `docs/admin/components.mdx` and `docs/admin/customizing-css.mdx`
Configuration menu - View commit details
-
Copy full SHA for 568e1a2 - Browse repository at this point
Copy the full SHA 568e1a2View commit details -
Configuration menu - View commit details
-
Copy full SHA for ff0386f - Browse repository at this point
Copy the full SHA ff0386fView commit details -
fix: prioritize server rendered Actions in ActionsProvider (#9379)
### What? Actions were not being re-rendered when router.refresh was called. [Discord Link](https://discord.com/channels/967097582721572934/1308636510203154462/1308648116031066173) ### Why? They were stored in state and the state was persisting. ### How? Spread the stateful actions and the Actions from props on top of the client state actions.
Configuration menu - View commit details
-
Copy full SHA for 439dcd4 - Browse repository at this point
Copy the full SHA 439dcd4View commit details -
Configuration menu - View commit details
-
Copy full SHA for ef37483 - Browse repository at this point
Copy the full SHA ef37483View commit details -
fix(next): properly sets doc id types when using postgres (#9381)
Fixes #9351. When using Postgres, doc ids were being treated as a string as opposed to a number within the admin panel. This led to issues for anything relying on the `docID` from context, such as the join field not properly populating initial data when creating new documents, etc.
Configuration menu - View commit details
-
Copy full SHA for 07a9125 - Browse repository at this point
Copy the full SHA 07a9125View commit details -
fix(richtext-lexical): use copy of @lexical/markdown that does not in…
…stall @lexical/code (#9382) Fixes #9378 We’ve found out that @lexical/markdown imports cannot be reliably dynamically imported by Node.js for an unknown reason. Frequently, Node.js simply exits before the dynamic import is done. We’re suspecting the reason for this to be its dependency on @lexical/code that installs prism. This will not only (hopefully) fix the import issue, but also reduce the bundle size & compilation speed of richtext-lexical.
Configuration menu - View commit details
-
Copy full SHA for 5db7e1e - Browse repository at this point
Copy the full SHA 5db7e1eView commit details -
fix(ui): invalid permissions passed to group and named tab sub-fields (…
…#9366) Fixes #9363 This fixes the following issues that caused fields to be either hidden, or incorrectly set to readOnly in certain configurations: - In some cases, permissions were sanitized incorrectly. This PR rewrites the sanitizePermissions function and adds new unit tests - after a document save, the client was receiving unsanitized permissions. Moving the sanitization logic to the endpoint fixes this - Various incorrect handling of permissions in our form state endpoints / RenderFields
Configuration menu - View commit details
-
Copy full SHA for c67291d - Browse repository at this point
Copy the full SHA c67291dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 025d917 - Browse repository at this point
Copy the full SHA 025d917View commit details
There are no files selected for viewing