-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add: get quote enabled for user query #51
add: get quote enabled for user query #51
Conversation
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
Quality Gate passedIssues Measures |
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
Actual version that was manually generated for this PR:
|
What problem is this solving?
Currently, frontend (
b2b-quotes
) calls thegetUserByEmail
API fromb2b-organizations-graphql
app to check if the user is part of a buyer org and, if it is, show the "My Quotes" button on "My Account" page.The
getUserByEmail
API returns much more stuff than necessary. Instead, now we have a much simpler query with restricted info on theb2b-quotes-graphql
app, which should be faster, less error prone, and will also simplify overall B2B Suite code.Related PR on
b2b-quotes
which will use this new API: vtex-apps/b2b-quotes#62