Schrank, 10 months ago

@bobmagicii not sure what you try, but in my mind just forms $User(‚admin‘) with __invoke. And I’m not sure how serious this should be 😅🙈🤪

shudder, 10 months ago

@bobmagicii Whenever there's a context for non-object it should always be a Null object.

Primitive null is not a mistake itself, but it should be like virtual photon - use it to exchange information between adjacent particles, but don't let it travel.

bobmagicii, 10 months ago

@shudder classifying it as a should, is debatable.

things like, im not going to transmit you json for a full empty user. you're gonna get a null.

then there are things like resource usage. was your infrastructure depending on 60% of your users not being logged in to have enough ram 🤣

shudder, 10 months ago

@bobmagicii Everything is debateable if you have enough time. At this point I don't know how many clarifying questions I need to get it on topic.

For example:

• What do you mean by "you get a null"? A client object? (that's not what I described as "traveling null") API user? (that would be more like empty body for 4xx response)
• Why do you accept empty user if you don't want to respond to it?
• What makes the difference between asking NullUser if he's registered and checking it for null?