If there is no value in the response parameter of the REST API, which should I choose, null or empty?

I'm developing a backend API and some response parameters do not have a value (such as null on DB) and I'm struggling with the design whether to return it as null or empty to match the type.

Currently, it is not unified, so the caller decides and absorbs it, but which one is better suited to?

api

2022-09-30 19:34

1 Answers

It's more of an opinion than an answer.

If you are preparing for an empty string to be "possible data", you should unify it to null or 0 if the data does not exist or has no meaning.
Currently, if there is no empty string, I think it would be a reality to prioritize the unification and decide on the one with the smaller amount of correction.

2022-09-30 19:34

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656