[WW-4258] Fix baseProjectRef for migrated configs#57
Open
Conversation
For migrated configs without baseProjectRef field, the branches endpoint was receiving an empty baseProjectRef parameter. Now falls back to the computed baseRef value extracted from projectUrl.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes issue where migrated Supabase configurations were sending an empty baseProjectRef parameter when loading branches.
For configurations migrated from legacy format, the baseProjectRef field is not present. The code now falls back to the computed baseRef value (extracted from projectUrl) when cfg.baseProjectRef is not available.