[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 swissspidy):

 > I think the time to have discussed this was during the development of
 this class in Gutenberg's development cycle. At this stage, the class has
 already been through Gutenberg's development, release, feedback, and
 testing cycles.

 Just a general observation / food for thought: I don't necessarily agree
 with this. Gutenberg development is so independent and different from core
 that only few core contributors keep track of what's going on there. And
 when we learn about a change (like with this ticket), it's often too late
 to make substantial changes. Then we have to deal with the consequences of
 doing last minute bug fixes and reverts because of a lack of code quality.

 > this kind of change needs to brought up at the project-level. It's an
 interesting discussion that warrants a more broad, project-level
 consideration.

 I do 100% agree with this though. I hope the community summit helps with
 this.

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