[pull] main from directus:main - #630
Merged
Merged
Conversation
* Add a refresh signal composable Provides an injectable counter an item form can bump when its item is re-read from the API, so descendants that fetch data of their own can refetch it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Expose a refresh signal from useItem Bumped in `refresh()` only, so the initial load and silent version refetches don't make consumers duplicate the request they already perform on mount. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Refetch relational rows when the item is refreshed Rows shown by relational interfaces are fetched separately from the item they belong to, so refreshing the item left them stale. Fold the injected refresh signal into the existing watchers rather than adding new ones, so a change that bumps the signal and the item id at once still results in a single request. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Provide the refresh signal from the content item route Fixes relational fields (O2M, M2M, M2A, translations, files) showing stale values after a manual flow updated them, and covers the other paths that re-read the item underneath an open form: AI tool results, live preview saves, and publishing a version. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Provide the refresh signal from the item drawer Manual flows also run on `location: 'item'` from within the drawer/modal item editor, so relational fields there went stale the same way. The drawer shadows the signal for its own descendants, which keeps a nested refresh scoped to the item that was actually re-read. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Add a changeset Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Cleanup * Apply feedback --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Alvaro Saburido <alvaro.saburido@gmail.com>
* Implement WYSIWYG content handling for unsupported markup in comparison modal * Refactor normalization diff handling and improve comparison schema integration - Updated `computeValueNormalizationDiff` to support schema-based caching for improved performance. - Introduced `comparisonSchema` function to manage extensions and schema keys for comparison mode. - Enhanced `useNormalizationWarning` to utilize schema keys for normalization checks. - Adjusted `useComparison` to incorporate new comparison schema logic, ensuring accurate diff marking. - Updated related tests to validate new functionality and caching behavior. This refactor aims to streamline the handling of rich text normalization in comparison views, enhancing performance and maintainability.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )