You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
interface RecommendLink <: Parent {
type: "element"
recommendLinkId: string // these are taken from the XML attributes
title: string
children: [Element | Comment | Text] // TODO: do we want to define this strictly, or allow elements?
}
We are not going to implement the <experimental> tag. Things that are currently being published inside that tag should have definitions.
maybe if we need this kind of functionality, we should introduce a property. But lets not.
For references, CP will still iterate through the AST to create the references array
This repo can provide Node definitions for "complete" nodes (i.e. a tweet with all teh embed stuff)
we can also provide helper functions to get the data (e.g. given a tweet ID, get the embed), which can be used in both CP and Spark Preview if required
somehow in our node definitions, differentiate between things which have an ID OR content
e.g.
<experimental>tag. Things that are currently being published inside that tag should have definitions.