feat(sanity): align portabletext with react v6.2.0 - #44
Merged
Merged
Conversation
commit: |
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
1 similar comment
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
osnoser1
force-pushed
the
codex/portabletext-react-6-2-parity
branch
from
June 10, 2026 22:19
3f1aa47 to
7ee85e3
Compare
osnoser1
force-pushed
the
codex/portabletext-react-6-2-parity
branch
from
June 10, 2026 22:34
7ee85e3 to
f407ee3
Compare
osnoser1
marked this pull request as ready for review
June 10, 2026 22:37
osnoser1
force-pushed
the
codex/portabletext-react-6-2-parity
branch
from
June 10, 2026 23:42
cf92378 to
f7beec8
Compare
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.
PR Checklist
Current behavior: the Angular portabletext renderer was based on older
@portabletext/reactbehavior and was missing the v6.2.0 public API/runtime parity added upstream.Closes: N/A
What is the new behavior?
@portabletext/reactv6.2.0 behavior where it maps cleanly to Angular.listNestingMode,defaultComponents/mergeComponentsexports, thePortableTextalias,unknownTypefallback support,renderNode/indexprops, and function-styleblock/list/listItemrenderers.toPlainText.@portabletext/reactv6.2.0.Does this PR introduce a breaking change?
Existing Angular inputs and component override shapes remain supported. New renderer props are supplied internally, and
indexdefaults to0for direct component usage.Other information
Verified with:
pnpm --filter @limitless-angular/sanity lintpnpm --filter @limitless-angular/sanity exec tsc -p tsconfig.lib.json --noEmitpnpm --filter @limitless-angular/sanity testpnpm --filter @limitless-angular/sanity build[Optional] What gif best describes this PR or how it makes you feel?