-
Notifications
You must be signed in to change notification settings - Fork 839
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
Schema auto-fetch doesn't run pre-request scripts correctly #11899
Comments
Is this issue in the v1 GraphQL client or in the beta v2 GraphQL client? |
How would I check? I sent this to Postman support and they sent me here because "GraphQL is in beta" — I didn't even realize there was a non-beta option 🙂 |
Oh, I see, I was totally unaware of the new beta client. The issue I reported is in the HTTP client. Screen.Recording.2023-04-04.at.6.54.11.PM.mov |
That makes sense. I appreciate the clarification and thank you for the gif! I'll pass this to the right team! |
Is there an existing issue for this?
Describe the Issue
GraphQL request in a nested folder doesn't run pre-request scripts from all ancestor folders
Steps To Reproduce
This is a show-stopper because in my case A has a PRS that setups up some globals that the PRS in B uses, so the PRS for B completely fails, and as. result the schema auto-fetch doesn't have the credentials it needs to succeed
Screenshots or Videos
No response
Operating System
macOS
Postman Version
10.12.10
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
Probably related to #10957 but in my case one of the scripts is running and the other isn't.
The text was updated successfully, but these errors were encountered: