This repository was archived by the owner on Feb 6, 2024. It is now read-only.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Accidentally closed #130 - moved feature to a branch to track separately.
Added Rails engine "namespace" to asset paths when installing CASino. Added migrations generator to copy migrations because the built-in
rake railties:install:migrationsdoes not work when running the command on a Rails engine. It's a simple fix to copy the files.Given, we may have a special case where we're mounting CASino in another mountable Rails engine.
You can test this by creating a mountable Rails engine, and mounting CASino. Then (from the rails engine root) try running the generator
rails g casino:installor the Rake commandrake casino:install:migrations. It doesn't seem to work (with the old code), but works now with this new generator.