[wp-trac] [WordPress Trac] #48329: Show Gutenberg version in Core
WordPress Trac
noreply at wordpress.org
Fri May 8 11:25:09 UTC 2020
#48329: Show Gutenberg version in Core
-----------------------------------------+---------------------
Reporter: mapk | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone: 5.5
Component: Site Health | Version:
Severity: normal | Resolution:
Keywords: has-screenshots needs-patch | Focuses:
-----------------------------------------+---------------------
Comment (by Clorith):
So, just to add some other points to the discussion, which will need
discussing/clearing up.
The ticket uses Gutenberg/Block editor as synonyms, which is not the case.
Do we need to separate out the packages somehow, is that needed? For
example "Gutenberg" as we view it is really a collection of a lot of NPM
packages built together, all with different versions.
It should also be noted that using the Gutenberg plugin version as a
reference to "Block editor" in core is also wrong. Gutenberg is a much
larger codename (gah, the confusion) which covers not only the block
editor, but also menus, widgets, full screen editing, customizer, it's way
too much and shouldn't be filed in one pile, for consistency, what if a
minor version backports a fix to a smaller components, and not to the
whole editor, which would make the number shown be misleading.
Do we instead of listing packages and versions, need to list components
and versions?
Example as of the time of this writing in trunk:
- Block editor version 3.7.8 (based on the package `@wordpress/block-
editor`)
- But also; Block editor version 9.12.8 (based on the package
`@wordpress/editor`) - what's the distinction here, and which takes
priority?
- Customizer version x.y.z (based on the package `@wordpress/customizer`
which does not exist yet)
- Menus version x.y.z (based on the package `@wordpress/menus` which does
not exist yet)
- ... and so on
But I'm not comfortable using just the Gutenberg plugin version as a
reference point, as it's incorrect, and what happens when we're all happy
with how things are and stop using the plugin and it's just "core" again,
things like that :)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/48329#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list