I had a few talks with @Inkdpixels today about dependency injection and stuff. There is a loose idea of having an index of classes, that can be accessed by a yet-to-write(tm) DI library and that also could be shared with componentdomparser.
In a framework context it would be easy to add a build step, that automatically generates that index, so there's no hassle to maintain it.
I could take my shared scope library and transform it into something that could fulfill our needs regarding that with the benefit of it offering access to application dependencies accross different application contexts.
Here's the link: https://github.com/PackageFactory/pflibs--shared-scope
@Inkdpixels @akoenig What do you think?
EDIT:
btw: let's call it @reduct/matrix -> no naming discussion there, huh? :P
I had a few talks with @Inkdpixels today about dependency injection and stuff. There is a loose idea of having an index of classes, that can be accessed by a yet-to-write(tm) DI library and that also could be shared with componentdomparser.
In a framework context it would be easy to add a build step, that automatically generates that index, so there's no hassle to maintain it.
I could take my shared scope library and transform it into something that could fulfill our needs regarding that with the benefit of it offering access to application dependencies accross different application contexts.
Here's the link: https://github.com/PackageFactory/pflibs--shared-scope
@Inkdpixels @akoenig What do you think?
EDIT:
btw: let's call it @reduct/matrix -> no naming discussion there, huh? :P