You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've bumped into a strange problem when bundling my gems inside my project's /vendor/bundle directory, it looks like stasis is attempting (and failing) at executing controller.rb files inside the stasis gem directory.
Maybe stasis should ignore all controller.rb files found under this directory ?
The text was updated successfully, but these errors were encountered:
This problem is getting really annoying ; could someone at least point me to where the controllers are searched and loaded so that I can try and fix the problem ?
Yep, from what I've read in stasis's code the controllers are first rounded up then executed, si whatever's in the main controller doesn't do much.
For now I've worked around it by creating a subdirectory under my main project so the vendor isn't a subdirectory when I'm calling stasis, and I'm working on a way to exclude /vendor altogether from looked-up directories when it comes to templates and controllers. I'll send a pull request when I'm done.
I've bumped into a strange problem when bundling my gems inside my project's /vendor/bundle directory, it looks like stasis is attempting (and failing) at executing controller.rb files inside the stasis gem directory.
Maybe stasis should ignore all controller.rb files found under this directory ?
The text was updated successfully, but these errors were encountered: