-
Notifications
You must be signed in to change notification settings - Fork 778
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
kv:get errors out reading --preview key if key is not in JSON format #359
Comments
Oh hmm I'd fixed this a while ago, but my fix got lost along the way. Will fix and add a test. Sorry about this! |
threepointone
added a commit
that referenced
this issue
Feb 1, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through.
threepointone
added a commit
that referenced
this issue
Feb 1, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through. Fixes #359.
Merged
threepointone
added a commit
that referenced
this issue
Feb 1, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 1, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 1, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through. Fixes #359.
🤘 |
threepointone
added a commit
that referenced
this issue
Feb 2, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case 'raw' requests to simply send the text through. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 2, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case for `kv:key get`. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 2, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case for `kv:key get`. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 2, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case for `kv:key get`. Fixes #359.
threepointone
added a commit
that referenced
this issue
Feb 2, 2022
The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the `FetchResult`-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like #359. The fix is to special case for `kv:key get`. Fixes #359.
Merged
This is fixed in #360, we'll do a |
GregBrimble
pushed a commit
that referenced
this issue
Feb 8, 2024
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GregBrimble
pushed a commit
that referenced
this issue
Feb 9, 2024
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GregBrimble
pushed a commit
that referenced
this issue
Feb 9, 2024
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This was referenced Feb 10, 2024
This was referenced Feb 17, 2024
This was referenced Feb 24, 2024
This was referenced Mar 4, 2024
This was referenced Mar 12, 2024
This was referenced Mar 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wrangler 0.0.15
Expected:
kv:get
returns the key requestedActual: Errors out complaining that it's not JSON
The text was updated successfully, but these errors were encountered: