Skip to content
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

Inconsistent FileOptions Between JavaScript and C# Supabase Clients #636

Open
Barlock42 opened this issue Feb 25, 2025 · 1 comment
Open
Labels
bug Something isn't working

Comments

@Barlock42
Copy link

Description:
The FileOptions class in the C# Supabase client does not support all the options available in the JavaScript Supabase client. This discrepancy limits feature parity between the two implementations, making it difficult for developers to use the same configuration across different platforms.

Expected Behavior:
The FileOptions class in C# should support the same options as the JavaScript client, including:

duplex

headers

metadata

Reference:
For JavaScript implementation details, see Supabase JavaScript Storage Upload.

Actual Behavior:
Currently, the C# FileOptions class only includes:

cacheControl

contentType

upsert

Steps to Reproduce:

Try to use duplex, headers, or metadata in the C# client.

Observe that these options do not exist in the FileOptions class.

Suggested Fix:
Extend the FileOptions class in C# to include all options present in the JavaScript client for consistency and feature parity.

Environment:

Supabase C# SDK Version: 1.1.1

@Barlock42 Barlock42 added the bug Something isn't working label Feb 25, 2025
@Barlock42
Copy link
Author

Maybe i am mistaken and it should be issue to supabase-csharp repo. Sorry if so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant