Message of the day:
Release 4.5.0 is out. Changelog: https://docs.silverstripe.org/en/4/changelogs/4.5.0
SilverStripe 4 related information and questions.
You'd have to ask the team. I'm not sure if you're intending to help with core commits, or implement a common component as a (test/) module.
Core best avoided for now. Common component more realistic. Based on the quick look at the source, there might be some benefit to provide an example of a two steps approach to component writing, a container component closely tied to the framework, a widget that can be updated/modified/tested without having to install the framework.
I don't follow, I'm not a front end person sorry. But it sounds neat. Just give it a blast :)
@marielle I like that idea, if an example can be provided to the team, I'd be happy to review it 🙂
a bit of my time has been to untangle the deep coupling some of these components/containers have...
@flamerohr do you have suggestions for an example. Given that there will be changes, to get them prepared to consider them, I must do something useful to them.
I don't have one off the top of my head, will need to have a proper look
asset-admin issues list would be my suggested "go to" for searching for one
I will start there, thanks.