Closed (fixed)
Project:
Commerce Core
Version:
8.x-2.x-dev
Component:
User experience
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 Jul 2017 at 16:10 UTC
Updated:
22 Aug 2017 at 12:39 UTC
Jump to comment: Most recent
Comments
Comment #2
bojanz commentedComment #4
bojanz commentedDone.
Comment #6
bojanz commentedI had to revert because this could complicate #2885483: Improve the Commerce configuration UX, need to make a decision there first.
Comment #7
joachim commentedI'm not sure about this. I get the idea that stores are something you don't change much, and could be tucked away, but from a developer's POV, it's nice to have content entities in the main menu and config in the submenu.
Comment #8
bojanz commented@joachim
Ecosystem-wise we're already not respecting that split, because shipping methods are content entities and they are under config.
It's the same case as stores, where we use content entities simply because we couldn't use config entities (due to machine names and them being limited in number)
Comment #10
bojanz commentedRe-committed.