-
Notifications
You must be signed in to change notification settings - Fork 23
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
v10 typing includes EntryFieldTypes, but mismatches actual API response #258
Comments
|
I'm running up against a similar issue when it comes to resolved links within embedded entries inside rich text fields. Not sure if this is an issue with this library or with the In this example, I'm creating a hero component based off of a hero content type. The data that I have access to inside the component I'm rendering for the embedded asset matches the I'm able to work around this by doing Sorry if this description is a little confusing. I can elaborate if you need me to. |
@jacksonopp You’re right. Resolved inks in rich text fields are currently not covered by the types in contentful.js. Feel free to file a feature request in contentful.js itself. |
Closing this issue in favor of contentful/contentful.js#1921 |
Hi,
we would love to type our application with generated types from our contentful space.
When generating the types via CLI (with v10 flag activated), we get the following as a result
But the actual API response (for the fields) looks somewhat like this:
As far as I understand
EntryFieldTypes
is an extended Type which is an object withtype
andvalues
, but the API returns the strings for example directly - so they mismatch.Eventually I got a general misconception of how the type generation should work or do I need to adopt the API query? When Manually changing the Type from
EntryFieldTypes.Symbol
toEntryFields.Symbol
I get the expected behavior, but of course that is not a proper solution for this use case.The text was updated successfully, but these errors were encountered: