fix(generatedAnswer): map state with answerAPI #4684
Merged
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.
SVCC-4353
https://coveord.atlassian.net/browse/SVCC-4353
See #4681 for the V3 PR. 🍝 Copy pasta of the description 👇
The problem
Upon interacting with a stream response, all headless selectors relying on the
generatedAnswer
slice after a response fetched by the answerAPI client aren't working properly because the state of the answerAPI client is not mapped to the actualgeneratedAnswer
slice.e.g. the custom events
The proposed fix
The answer API client is now dispatching what is relevant to the
generatedAnswer
state. The selectors will then return the same value as the generated answer controller state whenever it gets its answer from the client getting its answer directly from reveal or from the answer api.