-
-
Notifications
You must be signed in to change notification settings - Fork 22
Rename abstract text
interface to literal
#17
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
Comments
Seems like a good direction to take, replacing |
@ChristianMurphy Thanks, I totes agree! Leaf was another thing I thought of, but that would prohibit the use of something that has both a value and children in the future (and a node without value or children could also be a “leaf”, as a concept). |
* Update to the new style of unist <syntax-tree/unist@8055bf4> * Rename `Text` > `Literal`, `TextNode` > `Text` (syntax-tree/unist#17) * Reword definitions * Add introduction, references, links to terms * Add common mixins for shared fields * Move enumerations to their own section * Add description of content models (GH-21) * Remove marking of YAML as non-standard Related to syntax-tree/unist#18 Related to syntax-tree/unist#17 Closes GH-21.
* Update to the new style of unist <syntax-tree/unist@8055bf4> * Rename `Text` > `Literal`, `TextNode` > `Text` (syntax-tree/unist#17) * Reword definitions * Add introduction, references, links to terms * Add common mixins for shared fields * Move enumerations to their own section * Add description of content models (GH-21) * Remove marking of YAML as non-standard * Make `list.ordered` optional (default: `false`) * Make `list.loose` optional (default: `false`) * Make `listItem.loose` optional (default: `false`) * Make `table.align` optional * Add references to CSS Text for alignTypes Related to syntax-tree/unist#18 Related to syntax-tree/unist#17 Closes GH-21.
* Update to the new style of unist <syntax-tree/unist@8055bf4> * Rename `Text` > `Literal`, `TextNode` > `Text` (syntax-tree/unist#17) * Reword definitions * Add introduction, references, links to terms * Add common mixins for shared fields * Move enumerations to their own section * Add description of content models (GH-21) * Remove marking of YAML as non-standard * Make `list.ordered` optional (default: `false`) * Make `list.loose` optional (default: `false`) * Remove `listItem.loose` (use `list.loose instead) * Make `table.align` optional * Add references to CSS Text for alignTypes Related to syntax-tree/unist#18 Related to syntax-tree/unist#17 Closes GH-21. Reviewed-by: Christian Murphy <Christian.Murphy.42@gmail.com> Reviewed-by: Ika <ikatyang@gmail.com>
* Update to the new style of unist <syntax-tree/unist@8055bf4> * Rename `Text` > `Literal`, `TextNode` > `Text` (syntax-tree/unist#17) * Reword definitions * Add introduction, references, links to terms * Add common mixins for shared fields * Move enumerations to their own section * Add description of content models (GH-21) * Remove marking of YAML as non-standard * Make `list.ordered` optional (default: `false`) * Make `list.loose` optional (default: `false`) * Remove `listItem.loose` (use `list.loose instead) * Make `table.align` optional * Add references to CSS Text for alignTypes Related to syntax-tree/unist#18 Related to syntax-tree/unist#17 Closes GH-21. Closes GH-24. Reviewed-by: Christian Murphy <Christian.Murphy.42@gmail.com> Reviewed-by: Ika <ikatyang@gmail.com>
text
interface to literal
The abstract text interface (nodes with a
value
) interferes with thetype: "text"
node provided by hast and mdast (and thetype: "TextNode"
provided by nlcst).Another downside is that
text
implies (and specifies)string
values on thevalue
field.Say unist was used for programming values, the value of
value
could be specified asnumber
, for example.I’m open to other names, but I’m searching for something close to “raw”, “leaf”, and whatnot.
/CC @ChristianMurphy What do you think?
The text was updated successfully, but these errors were encountered: