Skip to content

merge master into next #1422

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

Merged
merged 2 commits into from
May 20, 2025
Merged

merge master into next #1422

merged 2 commits into from
May 20, 2025

Conversation

grdsdev
Copy link
Contributor

@grdsdev grdsdev commented May 20, 2025

What kind of change does this PR introduce?

Bug fix, feature, docs update, ...

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

grdsdev and others added 2 commits May 19, 2025 13:02
* fix: merge global passed headers with default headers

* refactor: use URL type for manipulating urls

* use baeUrl directly

* use href
# Conflicts:
#	src/SupabaseClient.ts
@grdsdev grdsdev changed the base branch from master to next May 20, 2025 12:49
@coveralls
Copy link

Pull Request Test Coverage Report for Build 15137957467

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 9 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-3.6%) to 69.058%

Files with Coverage Reduction New Missed Lines %
src/SupabaseClient.ts 9 66.67%
Totals Coverage Status
Change from base Build 15117764068: -3.6%
Covered Lines: 106
Relevant Lines: 132

💛 - Coveralls

@grdsdev grdsdev merged commit 915c5d0 into next May 20, 2025
2 checks passed
@grdsdev grdsdev deleted the guilherme/merge-master-into-next branch May 20, 2025 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants