Reset content after scan (on "unPause")
See original GitHub issueAwesome component, thanks!
However I would like the option to redeem the same code again (in my case after it has been paused), something that isn’t possible at the moment because of:
watch: {
content (newValue) {
this.$emit('decode', newValue)
},
...
}
Since this.content isn’t updated once it’s set
A solution might be to add an ‘resetOnUnpause’-prop and add ‘paused’ to ‘watch’:
props: {
...,
resetOnUnpause : {
type: Boolean,
default: false,
},
}
watch: {
paused(newValue) {
if (this.resetOnUnpause && !newValue)
this.content = null
}
}
Is this something you might be willing to add or should I contribute myself?
Thanks again!
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Pause or Resume a Scan - Docs Tenable
You can pause scans that you want to temporarily stop. When you pause a scan, Tenable.io pauses all active tasks for that scan...
Read more >How to PAUSE and later RESUME the MSSE when it takes ...
The full scan by MSSE takes too long to complete. Is there any way to temporarily PAUSE the scan and later RESUME the...
Read more >Pause, Resume, or Cancel a Scan - TechDocs - Broadcom Inc.
Log in to the product to view the list of scans. · Click the plus sign icon to expand the row for the...
Read more >Pausing a scan - Qualys Discussions
This Scheduled Task: Scheduling help document says that the only ways to restart a paused scan are manually or via 'resume days', and...
Read more >Pausing and continuing scans - HCL Product Documentation
To pause a scan, click the Pause button on the toolbar (or click Scan > Pause). The Notice Panel appears, displaying: Scan is...
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
Ok, I see…
I guess the only other way for now is using
v-if
to destroy the component while validating on your server which is just little bit better than reloading the hole page but not much better.Thanks, and yeah. I’d like to keep everything as clean and tidy as possible. But of course this component should be as useful as possible too.
I actually like your solution there. I think it makes sense to do that by default. Not even conditionally with a prop. What do think could go wrong?
🎉 This issue has been resolved in version 1.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀