Meeting notes September 22nd 2016.
Naming
The decision has been made to go for a new name to have a clean break with the past.
ViewModels
- A tool to generate ViewModels is nice to have as it's in high demand
- There is need for a testing framework to test model mappings
- View model mapping functionality should be an independently and visibly testable component
- ViewModels should not have a dependency on MVC
- One step view model generation: determine trade-off in time to develop against benefits. The decision is that is is worth to build a one step approach for .Net
- The new solution should be able to expose the ViewModels as JSon
Modules
- A module in this context is defined as the combination of optional functionality consisting of both CM and Web Application elements
- Loading and configuring modules should be easy and repeatable for both the CM and CD sides
- The module loading mechanism in the MVC apps will be built as independent of the MVC component as possible. It should be possible to extend an (abstract) core module with modules depending on third party components like MVC or other modules
- Rethink the DXA modules architecture and functionality per module. There's a need to reset and investigate what is a module and what not and what is in them.
Manifesto
- We should be as open as possible. This is already in the manifesto, but now also agreed upon in the Steering Committee
Dependency Injection
- The DI framework choice should be open for developers
- Every component, class implementation should have an interface and should be able to be DI-ed
.Net Core
- Should be supported, even though CIL should have .Net Core support as well (currently on the backlog).
- Should be on the backlog for the merge project.
0 Comments