Trying to squeeze this in before the deadline, so I'll start with this - do you think we'll see issues around sort order conflicts similar to what we saw around rewrite conflicts? If we do, what are your initial thoughts on resolving them?
Solved! Go to Solution.
(Please accept response if it answers your question to make it easier to track outstanding issues. Or ask a follow up question. Thanks!)
Honest answer? Yes, there will probably be some conflicts. The immediate answer is system integrators can write a module to override the sort order conflicts if they do occur.
The longer term answer is we were considering changing numbers to say "I must be before/after module X". That is, no numbers but rather declare dependencies. We then work out an ordering to satisfy the constraints. (Do you remember this discussion in the Austin partner forum back then?) That is still the plan. At that meeting the feeling was sort orders were enough for now - get other stuff done first - which is what we are doing.
If it proves to be a real problem, we will accelerate this as an item. Since a system integrator *can* solve the problem, it is not a blocker. So very interested in real world feedback how much of a problem this is in practice. Can two extension developers just agree between them where conflicts are identified with a gentlemen's agreement? Or do we need something better.
Opinions welcome! Real world experience even more welcome!!!