Hierarchy of Anvil-standard exceptions?

[p.colbert]

If I have to invent one, then I would likely follow this:

Handling exception coming from the server/uplink modules

Yes, that’s right - the Anvil client/server exception system assumes that all exceptions have a single string in their args. Exceptions do not have the full range of expressiveness found in normal client-server communications. If a server call throws an exception type you haven’t registered, you’ll just get an undifferentiated AnvilWrappedError. (This is true on the Uplink, same as on the server or client. As you correctly guess, it’s the name passed to _register_exception_type() that’s used to…

In which case, I should define my own app-specific branch of the exception hierarchy. Rooted at (for example) class AppError(anvil.server.AnvilWrappedError).

Could I then use AppError as a base class for the branch? Or must I derive each of my exceptions directly from anvil.server.AnvilWrappedError?

If I can use AppError as a base class, then are there any special considerations I would have to take into account in building, using, and/or catching the derived classes?