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

Refactoring Jabberwocky.Glass.Autofac.Mvc into two separate projects. #25

Merged
merged 3 commits into from
Sep 8, 2016
Merged

Refactoring Jabberwocky.Glass.Autofac.Mvc into two separate projects. #25

merged 3 commits into from
Sep 8, 2016

Conversation

kmazzoni
Copy link
Member

Created Jabberwocky.Glass.Mvc and Jabberwocky.Glass.Mvc.Tests projects.
Moved, MVC code with no Autofac dependencies to new projects.

Having a project without Autofac dependencies could be pretty useful. Particulary in the Reusable Component Library.

@smithc
Copy link
Contributor

smithc commented Jun 27, 2016

Looks good. However, regarding versioning strategy, these are considered breaking changes.

Do you see any reason that we can't rev to v2 for Jabberwocky.Glass.Autofac.Mvc? Otherwise, we can forward the types, and deprecate the old versions of classes being moved and just do a minor release.

@kmazzoni
Copy link
Member Author

I agree these would be breaking changes but I guess, as I think about it, it's probably appropriate to try take the steps to allow for a minor revision rather than a major revision. I can look into updating this pull request to include type-forwarding, etc.

kmazzoni and others added 3 commits September 7, 2016 16:17
@smithc smithc modified the milestones: Jabberwocky.Glass.Autofac 1.1, Jabberwocky.Glass.Autofac 1.2, Jabberwocky.Glass.Autofac.Mvc 1.2 Sep 7, 2016
@smithc smithc merged commit 1b0b593 into Velir:dev Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants