Krešimir Čoko
Krešimir Čoko
Sounds great @matuzalemsteles, I'm excited to see your vision 😄
What are we doing about this issue @pat270 @jbalsas ? Do we know of any actionable steps to take here? Have we done the steps listed above: > Manage a...
My main concern is how this would impact the way Clay is developed? Would Clay still have an instant feedback loop while developing new components or maintaining existing ones? Or...
> [...] we should work towards bringing those benefits in some form to liferay-portal if we want to consider it This is the biggest thing IMO, removing the technical debt...
Maybe we could make an overview issue for Data Provider, listing all sub-issues and using it to update some of the descriptions. @matuzalemsteles @bryceosterhaus thoughts?
To me, this sounds like we anticipated usages of more breakpoints than needed. When I do this when developing components I've been taught to not anticipate and over-engineer the capabilities...
Is there any new information for someone looking to pick up this issue? @matuzalemsteles
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 mentions...
> ...but we never did anything about it in Clay itself. @wincent should we revive this issue or close it?
Alright, keeping it open so we know it's something we can work on when the time comes.