d4rkr00t / prosemirror-dev-tools Goto Github PK

After selecting node using node picker this node should be scrolled into view in state tab

Button to collapse all uncollapsed nodes in the tree view

Shall we add few more groups in history:

• Only selection changed (we have it now)
• Not empty selection changed
• Document changed

E.g. redux devtools

Now logging for attributes doesn't work even though they have the log button next to them

• Semantic release
• TravisCI
• Commitizen
• Linters
• Prittier for changed files

Add ability to save/restore state.

What needs to be done for MVP:

• Save state to local storage (ability to define a name for state snapshot)
• Restore state from local storage
• UI For interacting with saved state – basically list of saved states

Next iteration

• Empty state for snapshots

Next iteration

• Save/Restore selection

Next iteration

• Exporting state to file
• Importing state from file

Next iteration

• Renaming snapshots

Next iteration

• History (?)

Use * instead of version

There aren't any way now to log whole document only its content:

It's ugly now.

Changing selection generates a whole lot of events and they are mostly useless because document stays the same:

We need a way to collapse this events, but with ability to get them when needed (e.g. when i want to jump back to some selection).

Probably we could even make other visual representation for selection changes.

Jest

• transpile styled-components
• date-fns -> tinytime
• ????

Add more information into readme:

• Example how dev tools look like
• Documentation how to use them
• Example on codepen.io
• Logo
• Contributing.md
• License

When I try to install this package 'the npm way' I am not able to install v2.0.0. I already tried removing ~/.npm and local node_modules, but it always errors with

14 http fetch GET 200 https://registry.npmjs.org/prosemirror-dev-tools 141ms
15 silly registry:manifest no matching version for prosemirror-dev-tools@^2.0.0 in the cache. Forcing revalidation
16 http fetch GET 304 https://registry.npmjs.org/prosemirror-dev-tools 27ms (from cache)
17 silly fetchPackageMetaData error for prosemirror-dev-tools@^2.0.0 No matching version found for prosemirror-dev-tools@^2.0.0
18 silly registry:manifest no matching version for prosemirror-dev-tools@^2.0.0 in the cache. Forcing revalidation
19 http fetch GET 304 https://registry.npmjs.org/prosemirror-dev-tools 20ms (from cache)
20 silly fetchPackageMetaData error for prosemirror-dev-tools@^2.0.0 No matching version found for prosemirror-dev-tools@^2.0.0

in the log. When I run

$ npm install --save-dev prosemirror-dev-tools

npm installs v1.4.0. However, when navigating to the registry page, I get a JSON string back, which clearly states that the latest version is 2.0.0.

Looks like this module (or one of its dependencies) is using React context without declaring context types? Not sure why it wouldn't have been showing a warning before, but it probably got upgraded to an error for React 16.

Here's a minimal repro case -- I just took the example CodeSandbox setup and updated react and react-dom to 16.0.0. https://codesandbox.io/s/jnlljqm3nw

Otherwise it leads to unpredictable editor state.

It's currently impossible due to react-tabs. Probably need to change it to another package.

After bumping my PM version to 0.23 I get the follow error:

ERROR in /~/prosemirror-dev-tools/dist/cjs/state/modules/editor/index.js
Module not found: Error: Cannot resolve module 'prosemirror-model/dist/to_dom' in /node_modules/prosemirror-dev-tools/dist/cjs/state/modules/editor
 @ /~/prosemirror-dev-tools/dist/cjs/state/modules/editor/index.js 24:14-54

It appears to be as a result of:

import { DOMSerializer } from "prosemirror-model/dist/to_dom";

In PM v0.23, you should be able to import DOMSerializer directly via 'prosemirror-model'. I'm not sure if that will be backwards compatible with previous PM versions? Was there a reason for importing directly from to_dom in the first place?

Add webpack which should build commonjs module out of src folder.

[ ] Unscrollable lists

• Up and Down to move between items
• Enter to select – the same as click
• Shift enter – the same as double click

Is it even feasible? Do we have access to dom node from prosemirror node?