-
Notifications
You must be signed in to change notification settings - Fork 20
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
PackageScore fields can be null #10
Comments
@Rexios80 In this particular case I believe the correct behavior would be just to have those params nullable. The other option is to set a default value, but not sure if that would be the correct apporoach. |
Nullable fields makes the most sense to me |
@Rexios80 would you like to do a PR for this? If not I will try to get to it over the weekend |
I will if I have time. I'm going to have to do some testing to figure out what fields are nullable unless you happen to already know. |
@Rexios80 if you can double check would be great. |
If a package was recently updated, some of the information in PackageScore can be null. For example: grantedPubPoints and popularityScore. These should be handled by the client.
The text was updated successfully, but these errors were encountered: