[wp-trac] [WordPress Trac] #57487: Add support for "development mode"
WordPress Trac
noreply at wordpress.org
Thu Jun 29 06:08:26 UTC 2023
#57487: Add support for "development mode"
-------------------------------------------------+-------------------------
Reporter: azaozz | Owner: flixos90
Type: enhancement | Status: closed
Priority: normal | Milestone: 6.3
Component: General | Version:
Severity: normal | Resolution: fixed
Keywords: has-patch has-unit-tests needs-dev- | Focuses:
note |
-------------------------------------------------+-------------------------
Comment (by peterwilsoncc):
The origin behind this ticket is that environment types defined in Core
are not mutually exclusive and have lead to problems. I think that as
implimented this code has the same problem.
Code will need to check multiple development modes (theme|plugin|core)
which Ozz identified in [comment:10 comment #10] as problematic for
environment types.
As this is going in to core, introducing the problem it is trying to solve
is inadequate.
I like @knutsp's suggestion in [comment:36 comment #36] of passing a
`$mode` parameter and returning a boolean if it matches either exactly or
by definition.
Replying to [comment:26 flixos90]:
> Good point, there may be cases where both are being developed. I think
`core`, `plugin`, and `theme` are the natural first choices, but happy to
explore adding more. I think this could happen either as part of an
initial commit or as a follow-up.
I think missing on `site` (or whatever it ends up being called) is to miss
the most common development mode for WordPress. In my experience at both
small and large agencies, site wide development is the norm and
exclusively developing either a theme or plugin is an exception.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57487#comment:45>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list