This repository was archived by the owner on Feb 6, 2024. It is now read-only.
Open
Conversation
Contributor
Author
|
@pencil any reason this was not pulled in? |
Contributor
Author
|
@pencil can this be merged in? |
Contributor
Author
|
@pencil any interest in pulling this in? I think it's very reasonable not to have to be forced to use |
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.
2 participants
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.
Create a configurable way to specify a superclass for
CASino::User. This allows CASino to become an extension of an existing application, where the "user" is the joining model for many other relationships. This is a clean way to make sure the "user" association on other CASino models are of the proper user class as well.