supabase/storage-js

`createSignedUrls` response does not match type

bombillazo opened this issue · 2 comments

bombillazo commented

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

The response for the createSignedUrls data is not the same as the actual data returned by the function.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Call the createSignedUrls function and compare with the typed data.

Expected behavior

Consistency between response data and type.

Screenshots

Response type:
image

Actual Data:

[
  {
    error: null,
    signedURL: "/object/sign/public/users/05e60ccc-f249-41fa-a358-38d6a9c36e74/file.txt?token=eyJhbGciOiJIUzI1NiIsIn...",
    signedUrl: "http://supabase_kong_hyperion-app:8000/storage/v1/object/sign/public/users/05e60ccc-f249-41fa-a358-3..."
  },
  {
    error: null,
    signedURL: "/object/sign/public/users/05e60ccc-f249-41fa-a358-38d6a9c36e74/file(1).txt?token=eyJhbGciOiJIUzI1NiI...",
    signedUrl: "http://supabase_kong_hyperion-app:8000/storage/v1/object/sign/public/users/05e60ccc-f249-41fa-a358-3..."
  }
]

System information

  • Version of supabase-js: 2.26.0
bombillazo commented

any update on this issue?

bombillazo commented

Update?