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, the 3scale-cms code makes use of generic exceptions. In order to provide clarity and better description of the exceptional cases, as well as facilitating programmatic handling of the exceptions, the 3scale-cms client code should implement new exceptions. 3scale CMS exceptions should each descend (directly or indirectly) from RuntimeException
For example, when client code that's generated from the OpenAPI spec throws ApiException, the exception should be interrogated for information to use with throwing a new 3scale-cms-specific exception.
The text was updated successfully, but these errors were encountered:
* Do not send empty layout ("") for new pages
* Use application/x-www-form-urlencoded for template create requests
* Do not handle tag_list on files as it's not part of the API anymore
* Add an Exception hierarchy
* Refer to the API using its official name Developer Portal API instead of Content Management API
* Remove distinction between ErrorHash and plain Error objects in OpenAPI doc
ResolvesFwMotion#99ResolvesFwMotion#16
Currently, the 3scale-cms code makes use of generic exceptions. In order to provide clarity and better description of the exceptional cases, as well as facilitating programmatic handling of the exceptions, the 3scale-cms client code should implement new exceptions. 3scale CMS exceptions should each descend (directly or indirectly) from
RuntimeException
For example, when client code that's generated from the OpenAPI spec throws
ApiException
, the exception should be interrogated for information to use with throwing a new 3scale-cms-specific exception.The text was updated successfully, but these errors were encountered: