COM-8341: Avoid calling getb2b user api. #466
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are not using this get b2b account API. So removed this. We are calling getUsers API in getB2Baccount api success which is causing weired issue of sending getB2Baccount reponse as getUsers api request We need to find different solution to fix such issues. eg: by reInitilizing model But in this case we do not need getB2B api so removing this will fix the issue..
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We are not using this get b2b account API.
So removed this.
We are calling getUsers API in getB2Baccount api success which is causing weired issue of sending getB2Baccount reponse as getUsers api request We need to find different solution to fix such issues. eg: by reInitilizing model
But in this case we do not need getB2B api so removing this will fix the issue..