7.0.0 Feature Planning

[SethDavenport]

@angular-redux/form needs a revamp. Since we've started working on a 7.0.0 release roadmap for /store@7.0.0 (https://github.com/angular-redux/store/projects/2) this seems like a good opportunity to re-work /form in the same timeframe.

[SethDavenport]

I'd like to get some input from the community about how you'd like to see redux+forms+ angular working together.

CC: @clbond @danielfigueiredo @renvrant @GenZodd @e-schultz @frederikaalund

[SethDavenport]

For now, feel free to dump ideas in here. Since it's a major version, breaking changes or even a complete rewrite are possibly in scope.

[frederikaalund]

I'd like to see bidirectional data flow between redux and the forms.

I'd like to point your attention to my own go at an angular-redux/form directive that implements bidirectional data flow.

This is nice to have when some service/other component is updating the store and the form needs to instantly reflect the updates.

Also, if two forms are connected to the same store, changes made to any one form will instantly apply to the other. This strengthens the visual cue that these two forms are indeed representing the same data. Each form may represent said data differently (e.g., a slider and a number input).

[olaf89]

I would like to have access to actions which are dispatched, to handle them in other reducers.
I would like to have possibility to dispatch actions handled by forms myself.
I would like to use template driven forms, with not much api overhead.
I would like to be able to mount store myself.

[GenZodd]

Currently, on form submission the form values are flushed from the store. I would like to be able to control this as when validating a form this can cause the store data to be cleared even though the fields still hold the values and the user is still trying to submit. This feeds into the bidirectional flow.

I would like to be able to use template forms
I would like to be able to use reactive forms

[smithad15]

• Splitting up the module definition to allow for the directives to be included in multiple modules without re-providing the forms store
• Getting the test suite working again and CI added
• Possibly reworking the build chain to better reflect the Angular Package Format (could be useful across all of angular-redux actually)

[SethDavenport]

Definitely agree on the Angular package format thing, across all three packages. Feel like taking a stab?

[smithad15]

Could do. The trick, as usual, will be finding the time :)

[rdinicut]

I think it will be very nice if the form will work with substores.

[jeffinmotion]

I'd love to see support for form validation. If that would be deemed too out-of-scope for the project, then more guidance on/recipes for.

[smithad15]

Validation is on my roadmap too. I’ve got a solution that I’m piloting on a project right now that I want to fold back into this library

[jeffinmotion]

That's great! I'm in a position where I'm basically about to roll my own validation w/ this lib for a project, so if there's even a chance you could share your in-progress solution, it would help. Knowing there's validation being thought out for this, I'll likely want to implement it in the future when it's released officially. Starting from roughly the same place would certainly make that easier. 😄

Does this mean that this package is going to be maintained? (Not meant as snark, genuinely asking)

[smithad15]

@KSuttle-cng As best we can considering the usual concerns of work / life / OSS balance 😄