- Notifications
You must be signed in to change notification settings - Fork673
chore: haveEncodedId
creation always returnEncodedId
#2040
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-commenter commentedMay 31, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## main #2040 +/- ##======================================= Coverage 93.68% 93.68% ======================================= Files 78 78 Lines 4985 4986 +1 =======================================+ Hits 4670 4671 +1 Misses 315 315
Flags with carried forward coverage won't be shown.Click here to find out more.
|
e2dcdb4
toc90cfa3
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM just one question :)
Uh oh!
There was an error while loading.Please reload this page.
There is no reason to return an `int` as we can always return a `str`version of the `int`Change `EncodedId` to always return an `EncodedId`. This removes theneed to have `mypy` ignore the error raised.
c90cfa3
toa1a246f
Compare
There is no reason to return an
int
as we can always return astr
version of the
int
Change
EncodedId
to always return anEncodedId
. This removes theneed to have
mypy
ignore the error raised.