Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stringifiability of other Node properties #5

Closed
eush77 opened this issue Feb 6, 2016 · 3 comments
Closed

Stringifiability of other Node properties #5

eush77 opened this issue Feb 6, 2016 · 3 comments
Labels
🙋 no/question This does not need any changes

Comments

@eush77
Copy link
Contributor

eush77 commented Feb 6, 2016

Do they have to be JSON-stringifiable as well? (I think they should.)

If they better be, is there a way to specify this?
@wooorm wooorm added 🙋 no/question This does not need any changes 🙉 open/needs-info This needs some more info labels Feb 6, 2016
@wooorm
Copy link
Member

wooorm commented Feb 6, 2016

Then you’re talking about properties not in the Unist core, such as start as defined by MDAST on the list node?

Anyway, this is related to what happens in GH-4.

@eush77
Copy link
Contributor Author

eush77 commented Feb 6, 2016

Then you’re talking about properties not in the Unist core, such as start as defined by MDAST on the list node?

Yeah, that.

@eush77
Copy link
Contributor Author

eush77 commented Feb 6, 2016

Closed in favor of #4.

@eush77 eush77 closed this as completed Feb 6, 2016
@wooorm wooorm removed the 🙉 open/needs-info This needs some more info label Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🙋 no/question This does not need any changes
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wooorm @eush77