I'm using shadow in a pretty unusual place, in an extensible browser game. It requires using classes for some pretty basic stuff but I can work that out likely without issue.

The trouble I've run into is shadow producing classes with $ as the delimiter to the classname to namespace classes

The thing wants to use the class name as a css selector

And these delimiters are making jquery choke

So I'm curious if it'd be hard to support a shadow config to change the delimiter, or to allow marking a class as unnamespaced?

I guess I could make it use a different character, but the things need to be namespaced because they end up living in the same "scope". so say you do (defclass Thing ...) in two different namespaces, they can't both be named Thing

but using the classname for something is kind of a problem, since it'll usually get compiled away in :advanced, or shortened or whatever

so can you override what name it uses maybe?

That's what I've been trying, and I even filed a bug report on their system that they break on valid identifiers and the only response I got was basically "lolno"

Because this is targeting a plugin like architecture though I'm not intending to go into advanced compilation.

is that engine open source? just curious what they are doing

It's FoundryVTT, not open-source unfortunately.

There's a lot of open source plugins for it though that I'm using to model how to write one

there are currently a lot of limitations in defclass, so you might be better off writing some classes in straight JS

Yeah, that's the option I'm evaluating as a next step.