cyril265
cyril265
You can still spoof data if you create a lvl1 char and send fake data for this char. Or am I missing something? Then again there is probably no real...
The warning says `PersonDto.g.cs(12, 22): [CS8669] The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive...
@andrerav I'm just going to mention you here, not sure if you are subscribed to this issue.
You could always rethrow the catched IOException if the error stream is null. Seems a bit hacky but it will fix all mentioned cases.
good thing there is a mechanism called javadoc to show which exceptions are thrown even if they are not checked.
I think the `RetryException` should stay checked because you always need to handle the case where all retries have failed. But it's kind of annoying to be forced to handle...
Really no particular reason 😃 I could probably migrade to jsonb. But it worked with jsonb[] in EF 7.
> So, as a user, you should carefully evaluate queries and see if you are expecting a null value appearing in left join and the property-accesses are able to accommodate...
lmao, how did you publish it? no build pipeline that runs npm install?