code data fields be removed

[Lpmvb]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

latest

Link to runnable example

https://node-rqtpry.stackblitz.io

Steps to reproduce

Expected behavior

Do not remove this field.

Actual behavior

data field be removed.

Runtime

Node v16

Package manager

npm v7

OS

macOS

Build and bundle tools

No response

[wooorm]

It is intended that the tree is changed and unrelated data lost, per the readme.
You can handle data fields in a plugin beforehand. Please open a discussion if you have questions about that.

[JounQin]

From #29

It is intended that the tree is changed and unrelated data lost, per the readme.

But in README

This package is a utility to parse a document again. It passes each node and embedded raw HTML through an HTML parser (parse5), to recreate a tree exactly as how a browser would parse it, while keeping the original data and positional info intact.

@wooorm I don't see any mentions of "unrelated data lost" , does anything changed?

I raised a new discussion at https://github.com/orgs/syntax-tree/discussions/148.

[wooorm]

The key is in all the other docs: parsing things again.
Everything (except positional info) is lost.

[wooorm]

If the words “original data” threw you off, we can discuss changing them

[JounQin]

If the words “original data” threw you off, we can discuss changing them

Can we discuss at https://github.com/orgs/syntax-tree/discussions/148?

You can handle data fields in a plugin beforehand.

And what about the afterhand? Non raw nodes are also affected.