Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[REQUEST] summary() should be added to form store
See original GitHub issueRight now summary() works great, but you can’t subscribe to it.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Add request summary to widget - ServiceNow Community
A use case for this would be if someone requested twenty of the same Catalog Item, each with different parameters (i.e. 20 VM...
Read more >Form to store additional information about requests
Stores text from the Summary field on AP:Show-Detail or the Comment field (if added) on the application form. If you add an activity...
Read more >Create, view, and manage marketing forms
Create, view, and manage marketing forms · Marketing form types and subscription behavior · Create and edit marketing forms · Form summary and ......
Read more >How to structure a web form - Learn web development | MDN
Using the correct structure when building an HTML form will help ensure that the form is both usable and accessible.
Read more >Change Request Form (Free Word Template) - ProjectManager
Use this free change request template to quickly fill out a change request form in Word. This is a crucial element in change...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Though I’m not in favour to adding another method to the store’s value (
$form) itselves, @eden-omb 's point is a valid one:There are methods on the form store and there are methods / properties on the store’s value. The only difference to a certain point is the use case: programatically or as a subscription inside a template. As an example:
hasErrorsits on the store’s value so it is going to be used inside a template. But at the same time in certain use-cases it would also be helpful to have this on the form itselves.I’m not sure where to draw the line here and if maybe there already have been some thoughts put into this, but it might make sense to explore this a bit further?
nice!