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
Auto-generated parity issue — may be a false positive.
This issue was created automatically by /sync-sdk-parity from a heuristic
analysis of recent supabase-js commits. The tooling has limited insight
into language-specific idioms and may have:
misidentified a JS-only change as cross-language relevant,
missed an existing implementation in this SDK under a different name,
or proposed an API shape that doesn't fit this language's conventions.
It is the SDK author's responsibility to validate the need before
implementing. If this change does not apply to this SDK, please close the
issue with a short note explaining why.
SDK Parity: C# implementation needed
A change was made in supabase-js that may need to be implemented in this repository for SDK parity. Please confirm applicability before starting work.
storage.from('bucket').list() has default search options including sortBy: { column: 'name', order: 'asc' }. When a caller provides a partial sortBy (e.g. only column, omitting order), the shallow merge replaced the entire sortBy default, losing the order field. The Storage server requires both column and order, so a missing order caused a 400 error.
The fix deep-merges sortBy so overriding only one of its keys preserves the default for the other.
Warning
Auto-generated parity issue — may be a false positive.
This issue was created automatically by
/sync-sdk-parityfrom a heuristicanalysis of recent
supabase-jscommits. The tooling has limited insightinto language-specific idioms and may have:
It is the SDK author's responsibility to validate the need before
implementing. If this change does not apply to this SDK, please close the
issue with a short note explaining why.
SDK Parity: C# implementation needed
A change was made in
supabase-jsthat may need to be implemented in this repository for SDK parity. Please confirm applicability before starting work.Reference Implementation (supabase-js)
42b7bbcWhat Changed
storage.from('bucket').list()has default search options includingsortBy: { column: 'name', order: 'asc' }. When a caller provides a partialsortBy(e.g. onlycolumn, omittingorder), the shallow merge replaced the entiresortBydefault, losing theorderfield. The Storage server requires bothcolumnandorder, so a missingordercaused a 400 error.The fix deep-merges
sortByso overriding only one of its keys preserves the default for the other.Code Reference
Current C# behavior (potential bug)
In
modules/storage-csharp/Storage/SearchOptions.cs:If a caller creates:
The server may reject this with a 400 since
orderis required.Implementation Guidance
Option 1: Default
OrderinSortByOption 2: Deep-merge in
List()In
StorageFileApi.cs, before building the request body, merge partialSortBywith defaults:Key Behaviors to Match
new SearchOptions { SortBy = new SortBy { Column = "updated_at" } }→ sendssortBy: { column: "updated_at", order: "asc" }new SearchOptions { SortBy = new SortBy { Order = "desc" } }→ sendssortBy: { column: "name", order: "desc" }new SearchOptions()(no SortBy override) → sendssortBy: { column: "name", order: "asc" }(unchanged)Files Likely Affected
modules/storage-csharp/Storage/SortBy.csmodules/storage-csharp/Storage/StorageFileApi.csAcceptance Criteria
SortBy(only Column or only Order set) fills in the missing field from defaultsSearchOptions()behavior unchangedContext
Generated with Claude Code
/sync-sdk-parity