We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When there is expand query parameter set, it doesn't stringify the fetch URL properly.
expand
For example, when I have { expand: ['free_web_content'] }
{ expand: ['free_web_content'] }
Result: https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=%5B%22free_web_content%22%5D Expected: https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=free_web_content
https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=%5B%22free_web_content%22%5D
https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=free_web_content
It seems that we use qs package. The issue is it doesn't process nested keys, which is documented on the site.
qs
(this cannot convert nested objects, such as a={b:1},{c:d}) – https://github.com/ljharb/qs?tab=readme-ov-file#parsing-arrays
(The documentation refers to parsing, but I assume that's the case of stringify-ing as well)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When there is
expand
query parameter set, it doesn't stringify the fetch URL properly.For example, when I have
{ expand: ['free_web_content'] }
Result:
https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=%5B%22free_web_content%22%5D
Expected:
https://api.beehiiv.com/v2/publications/:publicationId/posts/:postId?expand=free_web_content
It seems that we use
qs
package. The issue is it doesn't process nested keys, which is documented on the site.(The documentation refers to parsing, but I assume that's the case of stringify-ing as well)
The text was updated successfully, but these errors were encountered: