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
Currently, each resource implementation defines the same methods when available (find, find_one, create, etc.). Initially, it didn't make sense to abstract these methods into a base class since it wasn't clear how much overlap existed. But now, it's obvious that a majority of implementations between API endpoints are identical. In cases where endpoints differ, the subclass should override the base class. When the method is not supported a NotImplementedError should be raised and the method should be documented as such.
The text was updated successfully, but these errors were encountered:
Currently, each resource implementation defines the same methods when available (
find
,find_one
,create
, etc.). Initially, it didn't make sense to abstract these methods into a base class since it wasn't clear how much overlap existed. But now, it's obvious that a majority of implementations between API endpoints are identical. In cases where endpoints differ, the subclass should override the base class. When the method is not supported aNotImplementedError
should be raised and the method should be documented as such.The text was updated successfully, but these errors were encountered: