-
Notifications
You must be signed in to change notification settings - Fork 182
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
Why there is collision between @Nullable annotation and real explanation? #863
Comments
Hi, @ValeriusGC Of course in common case (for all operations except get().object()) result should not be null. @geralt-encore what do you think? |
Just a minute. |
Actually we can't prohibit nulls at all because we use the same interceptor interface for all operations. And one of them can return null |
We can, we can remove nullability annotation from interceptor to leave it
undefined
…On Thu, Dec 7, 2017 at 1:07 AM Dmitrii Nikitin ***@***.***> wrote:
Actually we can't prohibit nulls at all because we use the same
interceptor interface for all operations
<https://github.com/pushtorefresh/storio/blob/d968a579c0094179dc26747c2ea01a08d9a36286/storio-sqlite/src/main/java/com/pushtorefresh/storio3/sqlite/impl/DefaultStorIOSQLite.java#L267>.
And one of them can return null
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#863 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7B3Hk_mQhU8BrRGB_90AQKjqL6qtPJks5s96q4gaJpZM4Q4-1m>
.
|
Closed with #864 |
Hello.
Inspection warns me about possible NPE on insertedId() in the chain of
When i follow to the source i see
@Nullable
annotation and@return non-null results of Put Operation.
explanation. So, how one can interpret it?The text was updated successfully, but these errors were encountered: