-
Notifications
You must be signed in to change notification settings - Fork 5
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
refactor: move proteus errors to it's own top level error #761
Draft
typfel
wants to merge
1
commit into
main
Choose a base branch
from
refactor/proteus-errors
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
typfel
force-pushed
the
refactor/proteus-errors
branch
2 times, most recently
from
November 13, 2024 16:15
3409dd3
to
50cbaa8
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #761 +/- ##
==========================================
- Coverage 72.12% 71.72% -0.40%
==========================================
Files 106 106
Lines 19718 19822 +104
==========================================
- Hits 14222 14218 -4
- Misses 5496 5604 +108
Continue to review full report in Codecov by Sentry.
|
typfel
force-pushed
the
refactor/proteus-errors
branch
2 times, most recently
from
November 14, 2024 09:30
cf99aad
to
6af63f1
Compare
Moving proteus errors to it's own error struct lets us create more detailed proteus errors, which in turn will allow us to remove the proteus_code hack.
typfel
force-pushed
the
refactor/proteus-errors
branch
from
November 14, 2024 12:58
6af63f1
to
b05ef18
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's new in this PR
Moving proteus errors to it's own error struct lets us create more detailed proteus errors, which in turn will allow us to remove the
proteus_code
hack.PR Submission Checklist for internal contributors
SQPIT-764
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.