This Rails engine encapsulates the Javascript, CSS, and Ruby helpers shared across SurveyMonkey Business Solutions applications.
This is a Rails engine, initialized by Rails 5.0.2. If you are unfamiliar with engines, you'll notice the layout is very similar to a standard Rails applications. The main difference is that most of the code directories are one level deeper in an pano folder. This is how the Pano namespace is maintained.
One key difference between a standard Rails application is the pano.gemspec file. Rather than use the Gemfile to enumerate dependencies, gems must be listed in the gemspec.
Because an Engine is not designed to be run on its own, there is a special 'dummy' application that lives inside the spec/ directory. This test application loads the engine.
For local development, you'll actually want to mount the test application via pow, rather than the engine. The command would be something like ln -s /Users/username/dev/pano/spec/test_app/ /Users/username/.pow/pano. That will load the application at http://pano.dev. Remember! You must run bundle install from WITHIN the dummy application.
To use this engine, require it as a dependency in another Rails application's Gemfile. When you run bundle install within the host application, the Ruby helpers will be locked and the app/assets directory in Pano will become part of the lookup chain for Sprockets.
The root of Pano is mounted in the routes file, like so:
Rails.application.routes.draw do
mount Pano::Engine => 'style-guide'
end
And the helpers are imported into ApplicationHelper like this:
module ApplicationHelper
include Pano::Engine.helpers
end
You are now off to the races. You can reference any helper as you would expect. Assets are in the pipeline (just remember to prepend pano/), and modules are referenced like Pano::Menu.
In the host application, you'll likely want to refer to a local copy of the Engine, rather than the one on GitHub. To do this, instruct Bundler to look on your file system:
bundle config local.pano ~/dev/pano
You will need to run bundle update and rails restart (or rails update) in the host application to pick up changes. Updating bundle will also set the Gemfile.lock to that commit hash, so remember to push up any changes to Pano before deploying the host application.
To revert back to the GitHub engine, use:
bundle config --delete local.pano
Again, you will need to run bundle update and rails restart (or rails update) in the host application to pick up changes.
NOTE - If you notice CSS not updating in your project after making changes in Pano and verifying all your settings are correct, try rake tmp:cache:clear and a rails restart
After working with Pano locally, your project (CX, Engage) will need to use the latest revision of Pano before your next project merge. To do so, make sure your Pano commits are merged to master. Use the local development steps to revert from Pano local development to the Github engine. After doing so, your bundle install will reinstall the Pano engine in the project, updating your Gemfile and Gemfile.lock. These need to be merged in with any commits that are dependent upon that Pano revision.
In other words, do not merge commits for CX or Engage that depend on your changes to Pano until your changes to Pano have been merged into pano/master
Test specs are available in the ~/dev/pano/spec directory, alongside the test app.
To run the Pano test suite, in the root directory, use:
rake spec
https://www.dropbox.com/sh/esapsev12igl95f/AAAtknkC-FekF90KK5Dl2W8ya?dl=0