Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Normally, async computed properties work with debouncing
in the way the result of a change is not committed if other changes are triggered before the result is committed.
For example, if a source property is continuously changing every 100ms and API call takes 500ms,
normal async computed properties will not be changed until the change of the source property stops.
With this change set and non-debounce option, async computed properties will be updated with the last source value.
I think this behavior should be default in the next major version while non-debounce option is inevitable in most common usage.