Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix to issue 69 #71

Merged
merged 2 commits into from
Aug 29, 2011
Merged

Fix to issue 69 #71

merged 2 commits into from
Aug 29, 2011

Conversation

jcarroll3
Copy link

Managed to get a little free time and noticed that change I made wasnt too drastic. I added functionality to force base class to be set even if the user has entities with parent entities (--base-class-force). If the user just chooses --base-class there will be no changes in behavior from what they are used to.

Joe Carroll added 2 commits August 28, 2011 14:55
rentzsch added a commit that referenced this pull request Aug 29, 2011
[NEW] base-class-force option that uses the provided base class name even if a super entity exists (base-class option still functions normally). (Joe Carroll)
@rentzsch rentzsch merged commit d032e96 into rentzsch:master Aug 29, 2011
@rentzsch
Copy link
Owner

Looks good, pulled. It will be in the next release. Thanks!

ddrccw pushed a commit to ddrccw/mogenerator that referenced this pull request Jan 20, 2014
[NEW] base-class-force option that uses the provided base class name even if a super entity exists (base-class option still functions normally). (Joe Carroll)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants