…r the view. Needed to move the order in cases where the view subclassed a layout - the layout might not have been required yet, which would throw a NameError on mustache_class call
Specification compliance-testing code really belongs in the implementation repository. The Ruby test case has already been pulled out of the specifications module, and has now been replicated here. If the submodule is not populated, compliance testing is simply bypassed.
Previously this would work in unexpected ways. Now it behaves thusly: Given `mustache :"positions.atom"`, Mustache will try to find `Views::Positions::Atom`. If it finds it, it'll use it. If it can't find it, it'll create it as a subclass of `Views::Positions` and set the `template_name` setting to "positions.atom".
…_extension, @view_namespace, and @view_path