-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for external references #2294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good, I'll TAL at the build and see if I can see what's up
5ab2bb7
to
5430926
Compare
? ResolvedEntryLink<Modifiers, Locales, LinkedEntry> | ||
: Field extends EntryFieldTypes.EntryResourceLink<infer LinkedEntry> | ||
? ResolvedEntryResourceLink<Modifiers, Locales, LinkedEntry> | ||
: Field extends EntryFieldTypes.AssetLink | ||
? ResolvedAssetLink<Modifiers, Locales> | ||
: BaseFieldMap<Field> | ||
: Field extends EntryFieldTypes.ExternalResourceLink | ||
? { sys: ResourceLink<string> } | ||
: Field extends EntryFieldTypes.AssetLink | ||
? ResolvedAssetLink<Modifiers, Locales> | ||
: BaseFieldMap<Field> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there no other way to represent this? 😬
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by represent?
🎉 This PR is included in version 10.13.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
Add support for external references.
Description
Since these aren’t resolved they skip the
withoutUnresolvedLinks
behavior and are always kept.I’ve only updated the
parseEntries
part of the integration tests because it’s enough to cover the simple logic we currently have. The underlying behavior is the same forgetEntries
anyway. If we complicate the logic in the future we can expand the tests as well.