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

fix(macos): custom protocol response with status code + error response #279

Merged
merged 1 commit into from
May 20, 2021

Conversation

lucasfernog
Copy link
Member

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Documentation
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes. Issue #___
  • No

The PR fulfills these requirements:

  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

The macOS custom protocol handler wasn't returning a status code or an error response. Linux status code is always 200, i'll see if an error response is being returned. Also, I didn't check Windows yet.

@lucasfernog lucasfernog requested a review from a team as a code owner May 19, 2021 16:52
@lucasfernog lucasfernog requested a review from a team May 19, 2021 16:52
@lucasfernog
Copy link
Member Author

Linux works great on both success and error responses.

@lucasfernog
Copy link
Member Author

Windows works as expected too (error response and 200 status code).

@wusyong wusyong merged commit 6b869b1 into dev May 20, 2021
@wusyong wusyong deleted the fix/macos-custom-protocol branch May 20, 2021 05:14
This was referenced May 20, 2021
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