You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason being then only a singular object can be a context for similar but different components, engaging date pickers, sliders, and/or image uploads into a singular model. The components can manipulate their own slice of the object which is then shipped to the server.
Thanks for this awesome framework!!
The text was updated successfully, but these errors were encountered:
First of all, thanks for your contribution. We are discussing with the team if and how we should implement this feature. It may take a while, but we are most definitely going to share our findings/progress. In the meantime, I beg your patience.
If you have a suggestion on how to proceed, please do share.
For now I have bound properties to a form and view; just like your demo shows. That seems to work quite well. Just to give you more context (no pun intended!) I'm hoping to build a platform for users to put up messaging on web and mobile platforms. In the future, I'd like users to be able to design their own forms to display their own custom message models in their apps.
You can see the current project here. I hope that one day this will be a powerful demo of ngx-context as forms can be composed dynamically with no ts boilerplate.
Is your feature request related to a problem? Please describe.
I can't two way bind specific properties in objects that I assign to the context.
Describe the solution you'd like
Assuming I have this child template:
I'd like to be able to do this:
The reason being then only a singular object can be a context for similar but different components, engaging date pickers, sliders, and/or image uploads into a singular model. The components can manipulate their own slice of the object which is then shipped to the server.
Thanks for this awesome framework!!
The text was updated successfully, but these errors were encountered: