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

Extract ORMs from doorkeeper, take 2 #648

Merged
merged 2 commits into from
May 12, 2015
Merged

Extract ORMs from doorkeeper, take 2 #648

merged 2 commits into from
May 12, 2015

Conversation

tute
Copy link
Contributor

@tute tute commented May 4, 2015

Related PR: doorkeeper-gem/doorkeeper-mongodb#2

Idea:

  • Clone down and checkout doorkeeper when doorkeeper-orms runs rake
  • Configure doorkeeper to load orm's code and each of its ORMs, run
    doorkeeper tests after extending with ORMs

To do:

  • Move documentation removed from here into doorkeeper-orms project
  • doorkeeper-orms renamed to doorkeeper-mongodb
  • Move ORM specific generators (might be buggy)
  • Move ORM specific code fromspec/* to doorkeeper-mongodb.
  • If successful, release doorkeeper 3, document in both projects. Requires an app making sure documentation is correct.

Both projects see a good portion of their code bases removed, keeping same behavior, test coverage, and getting faster specs. WIN.

@tute
Copy link
Contributor Author

tute commented May 4, 2015

@jasl please tell me how you like these changes! I think this is a good way of solving this problem.

@tute tute force-pushed the extract-orms branch 2 times, most recently from 15f5b36 to 9ef5155 Compare May 4, 2015 02:43
@jasl
Copy link
Contributor

jasl commented May 4, 2015

Let's me check after work.

@jasl
Copy link
Contributor

jasl commented May 4, 2015

@tute I comment in doorkeeper-orms

@tute tute force-pushed the extract-orms branch 2 times, most recently from 7a860a1 to 0b0031e Compare May 5, 2015 04:03
@@ -26,6 +26,5 @@ Gem::Specification.new do |s|
s.add_development_dependency "timecop", "~> 0.7.0"
s.add_development_dependency "database_cleaner", "~> 1.3.0"
s.add_development_dependency "rspec-activemodel-mocks", "~> 1.0.0"
s.add_development_dependency "bcrypt-ruby", "~> 3.0.1"
s.add_development_dependency "pry", "~> 0.10.0"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jasl can we remove dependencies from here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think yes

@tute
Copy link
Contributor Author

tute commented May 5, 2015

It looks both PRs are green. Updated documentation in both repos, and renamed the mongodb extensions one.

We just need a real mongo doorkeeper application to make sure everything has been tied together correctly. Do you have anyone at hand, @jasl? Thank you!

@jasl
Copy link
Contributor

jasl commented May 5, 2015

No problem, I will update our application to doorkeeper edge version and test

@tute tute force-pushed the extract-orms branch 2 times, most recently from eacfc8d to cf38ddc Compare May 12, 2015 02:34
tute added 2 commits May 11, 2015 22:55
This PR removes doorkeeper ORM specifics, in favor of extending it with
other rubygems.

The specs defined in this project are still considered canonical, and
the goal is for extension rubygems to set doorkeeper as a git submodule,
and running its test suite against the specific ORM that is being
extended.

See doorkeeper-gem/doorkeeper-mongodb#2
tute added a commit that referenced this pull request May 12, 2015
Extract ORMs from doorkeeper, take 2
@tute tute merged commit 7fe4940 into master May 12, 2015
@tute tute deleted the extract-orms branch May 12, 2015 02:58
@jasl
Copy link
Contributor

jasl commented May 12, 2015

We have update our developing branch using this gem, if have problem, I will fix

@jasl
Copy link
Contributor

jasl commented May 12, 2015

oh I mean doorkeeper-mongo

@tute
Copy link
Contributor Author

tute commented May 12, 2015

I created a new 2.2-stable branch that will receive security fixes from now on. master is already tracking version 3, which I expect to release whenever we see a mongodb doorkeeper v3 installation working correctly, and making sure documentation is correct.

Thank you!

@tute
Copy link
Contributor Author

tute commented May 12, 2015

In preparation for Rails 3, if we still have changes we didn't do due to backwards compatibility concerns, or we have leftover upgrading warnings, we should change/remove those now.

@tute
Copy link
Contributor Author

tute commented May 28, 2015

@jasl could you test doorkeeper 3 with your MongoDB project, so we make sure it works and can release v3 stable?

@jasl
Copy link
Contributor

jasl commented May 28, 2015

OK, give me a week to test it stable.

This pull request was closed.
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