Client-side class source should automatically mimic Server-side class definition.

[codewillclick]

Let's debate this

• [x] Should the client class always mimic the server class' naming definition perfectly?
• [x] Should arbitrary classes be returnable from clientClass()?

[codewillclick]

But there are cases where this wouldn't be helpful. Like if an existing class name difference is derliberate.

... Does this indicate a need for a global obparity config object?

No, maybe static async getClientSource() should have a parameter for that? Same for async clientSource()?

That would indicate params for...

• bool: force the same class+extends names?
• bool: add in static methods = ...;, or leave it out?

[codewillclick]

So, as for those checkbox items...

• shouldn't always do so, but it's in a config object now, so we're good there
• I'm... gonna assume so ** the idea of overriding methods would imply an ability to do whatever the heck you want

Making the commit, then closing.