Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
Unlike DatoCMS and Contentstack, you cannot restrict a Contentful content model to be used to create a single record, only multiple (as per design).
-
TIL about scrollbar-gutter, a useful CSS property that forces a scrollbar gutter in lieu of the scrollbar itself when it normally wouldn't render (i.e. < 100vh).
-
As part of YouTube's TOS, the embedded player (i.e. iframe) must provide identification via the HTTP Referer header (not a typo unfortunately), otherwise you may end up with the following error: To remedy this, make sure it's at least set to strict-origin…
-
TIL about the genius of using an input="range" as a (programmable) scrollbar replacement when using the native one isn't possible.
-
In the following example, <price display="no">$500,000.99</price> <priceView>Between $400,000 and $600,000</priceView> the priceView text is not displayed in lieu of the price because display="no" actually hides everything price-related, toggling "Contact
-
Asset fields values are read as a regular object (i.e. with access to a filename, uid, etc.), and updated as a string that corresponds to an existing asset UID (using the CMA SDK at least).
-
Values for all fields within a multiple group must be provided, even if only one field has changed.
-
Query filters don't work how you'd expect them when combined with the fallbackLocales flag (i.e. filtering isn't conducted on "merged" data - because it isn't even available at that point).
-
Contentstack reference fields are returned as [] instead of null if empty in REST (at least compared to GraphQL lookups).