-
Notifications
You must be signed in to change notification settings - Fork 20
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
use stega options in loadQuery #1208
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For stega
to apply properly it needs to be extracted here:
const { query, params = {}, perspective, useCdn } = JSON.parse(key) |
And passed in here:
visual-editing/packages/core-loader/src/index.ts
Lines 122 to 127 in 1b248a7
const { result, resultSourceMap } = await client.fetch(query, params, { | |
tag, | |
filterResponse: false, | |
perspective, | |
useCdn, | |
}) |
Co-authored-by: Cody Olsen <[email protected]>
Co-authored-by: Cody Olsen <[email protected]>
@SimeonGriggs Are there any plans to merge this PR? |
Currently when passing
staga
config intooptions
it doesn't actually get used byloadQuery
.This has not been tested. I'm specifically unsure if the JSON.stringified version actually works...