You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You created this issue using the 🚨 Bug report template therefore it has been flagged as such.
Hi there, thank you so much for your contribution!
Following our Maintenance process, we will review your bug report and get back to you next Wednesday. To ensure a smooth review of your issue and avoid unnecessary delays, please make sure your issue include the following:
Information about your environment and packages you use (Node version, package names & versions, etc.) Feel free to attach a copy of your package.json file.
Any troubleshooting steps you already went through
A minimal reproduction of the issue, and/or instructions on how to reproduce it
If you have identified the cause of the bug described in your report and know how to fix it, you're more than welcome to open a pull request addressing it. Check out our quick start guide for a simple contribution process.
If you think your issue is a question (not a bug) and would like quicker support, please close this issue and forward it to an appropriate section on our community forum: https://community.prismic.io
Hi @akumanara, apologies for the delay in response. Thanks for reporting the issue and providing your workaround. It highlighted that the getTags() method was not properly sending the client's accessToken parameter to the Tags API endpoint.
This should be fixed as of #245. The fix is not published yet, but it will be included in the next version.
client.getTags() returns an empty array and i had to use the following to get the tags.
Replace my-repo-name with your repo name.
const url = new URL('https://my-repo-name.cdn.prismic.io/api/tags');
url.searchParams.set('access_token', client.accessToken);
let test = await client.fetch(url.toString());
The text was updated successfully, but these errors were encountered: