fix: add missing overrides to the supabase generator #422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR sits on top of #420, which fixed some generator issues as described in #416.
It specifically resolves the following errors:
The
Customer
model has noonConflict
specified in theSupabaseSerializable
, which results in the following runtime error because of the missing override:The
WindowType
model has noSupabaseSerializable
specified (because there is no corresponding Supabase table, it is used inside a JSONB field), and therefore thetableName
is null, which results in the following runtime error because of the missing override:I just noticed that the
supabaseTableName
is a non-nullable field on theSupabaseAdapter
, which means this PR is not ready as it is. @tshedor how should we handle this?