Navigation Menu

Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Augury feature for Forms #1016

Closed
rajinder-yadav opened this issue Mar 13, 2017 · 4 comments
Closed

Augury feature for Forms #1016

rajinder-yadav opened this issue Mar 13, 2017 · 4 comments
Assignees

Comments

@rajinder-yadav
Copy link
Contributor

rajinder-yadav commented Mar 13, 2017

We need to round up the feature set for working with Forms.

@rajinder-yadav rajinder-yadav self-assigned this Mar 13, 2017
@rajinder-yadav
Copy link
Contributor Author

I've got a demo app ready with forms for the Guide, will use it to consider ideas for Augury feature set.

@stevenkampen
Copy link
Contributor

@rajinder-yadav I think we need to make a proper investigation for any 'forms' specific features. I'm not sure that it will be necessary, or worth it, so I don't just want to jump straight to trying to think of something to do. The fact is, forms are very finicky, and everything is already available through component state. Trying to apply another layer on top of that seems like a lot of continuous work for very little pay off.

@rajinder-yadav
Copy link
Contributor Author

@stevenkampen I just plan to review if anything obvious is missing, my main objective is to complete the Forms guide and not really add more feature for Form to Augury. I agree with your comments.

@stevenkampen
Copy link
Contributor

resolved by #1043

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants