feat(ktable): expose table data and revalidate handle #2510
+3
−0
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.
Summary
KM-694
Currently, some consuming apps use
useSwrvRequest
while passing the fetcher with the same key to fetcher ofEntityBaseTable
which passes along this param toKTableData
.However, separate calls of
useSwrvRequest
in consuming app andKTableData
cause the same request being fired twice. So data andrevalidate
handle are exported for consuming app to watch, like ingateway-manager/CustomDomainList