[wp-trac] [WordPress Trac] #58555: Backport: Duotone changes, refactor, enhancements and fixes

[WordPress Trac]

#58555: Backport: Duotone changes, refactor, enhancements and fixes
-------------------------------------------------+-------------------------
 Reporter:  onemaggie                            |       Owner:
                                                 |  isabel_brison
     Type:  task (blessed)                       |      Status:  closed
 Priority:  normal                               |   Milestone:  6.3
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-unit-tests gutenberg-merge has-  |     Focuses:
  patch                                          |
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 Following up with a way forward for the architectural design pattern
 change being requested:

 @spacedmonkey I think this
 [https://github.com/WordPress/gutenberg/pull/48698#issuecomment-1517898717
 kind of change needs to brought up at the project-level]. It's an
 interesting discussion that warrants a more broad, project-level
 consideration.

 How to move it forward?

 An actionable and well argued Make/Core Proposal can be an effective way
 to advocate for an architectural design change, especially for a change
 that requires a particular design pattern not be used within the project.
 If adopted, then all new classes being introduced in Gutenberg and/or Core
 would need to comply to the new coding standards.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58555#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform