You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gut is yes, userIds should continue to be required.
There will never cases where you’re creating a note/category/etc for anyone except the current user, so we could just inject the AuthController and not have to provide it every time. But that doesn't seem like a good pattern to me, because there's nothing guaranteeing that the API calls will happen after the session has been updated. It leaves behavior entirely up to the runtime (i.e. assumptions about when the API will be called), which seems like an anti-pattern.
The text was updated successfully, but these errors were encountered:
Gut is yes, userIds should continue to be required.
There will never cases where you’re creating a note/category/etc for anyone except the current user, so we could just inject the
AuthController
and not have to provide it every time. But that doesn't seem like a good pattern to me, because there's nothing guaranteeing that the API calls will happen after the session has been updated. It leaves behavior entirely up to the runtime (i.e. assumptions about when the API will be called), which seems like an anti-pattern.The text was updated successfully, but these errors were encountered: