Greg Hurrell
Greg Hurrell
See #1070 as well, which is about making the editor easier to consume.
Seeing as this got mentioned recently, a couple of updates to my "prototype" since opening this issue back in February: > we also have that chicken-and-egg situation of not being...
> Did we end up making a centralized script runner abstraction as a response to this issue, or did it just stay in the limbo? @wincent The referenced PR only...
> @wincent should we revive this issue or close it? There is also a third option, which is do nothing. You folks who are working on Clay are in the...
I agree, @duracell80, consistency would be good here. The trash can is probably not a good fit: in my experience it is used for higher-level entities that can be considered...
Created internal ticket https://issues.liferay.com/browse/IFI-480 to track this.
Great news, I've found the commit that introduced the silent failures: eac6967c "Update mocha as recommended by `npm audit`". Going to dig deeper.
Thanks for the question @akjackson1. It's true that not much has been happening in AlloyEditor of late. I don't think there are any plans to archive it as such. We...
I think it's about achieving a practical, pragmatic balance between two things that both sound desirable in the abstract (ie. the two ends of the axis in your diagram: flexibility/generality...
> > @wincent > > It's made Clay harder to use than necessary for teams working in liferay-portal > > Any particular areas that have been hard about it? I...