Should we support Classic Editor and WordPress versions prior to Block Editor within this library?

[cadic]

When writing Block Editor related commands, I thought that it might be handy to make some of commands to be compatible with both approaches (Block vs Classic editor).

• Working with taxonomies on the Edit Post page
• Metaboxes
• Post/Page attributes
• Create new Post
• etc.

[dinhtungdu]

@cadic As discussed in the meeting, we should split those commands based on the current editor:

• As @peterwilsoncc mentioned, some custom post types may use Classic Editor only.
• Also, it's the developers/testers' responsibility to ensure which editor is being tested.

Because Blocks Editor is the default editor, I think we should, first, create commands for Blocks Editor, then create commands for Classic Editor with Classic in the command name.

[jeffpaul]

I concur with @dinhtungdu and think making this clear in the readme should suffice here?