I think the only hard dependency between Rbexy::Component and the rbx compiler is currently the rbexy_context wrapper in compiled output. Consider replacing this with a Rbexy.config.component_preamble / postamble or Rbexy.config.component_wrapper so it could be configured from the outside.
The default rbx component resolver could just try to constantize the component name. Rbexy::Component could provide a resolver that adds Component to the end of the name before resolving.
I think the only hard dependency between
Rbexy::Componentand the rbx compiler is currently therbexy_contextwrapper in compiled output. Consider replacing this with aRbexy.config.component_preamble / postambleorRbexy.config.component_wrapperso it could be configured from the outside.The default rbx component resolver could just try to constantize the component name.
Rbexy::Componentcould provide a resolver that addsComponentto the end of the name before resolving.