Skip to content
This repository has been archived by the owner on Aug 24, 2021. It is now read-only.

Updated SDK #20

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

chriskaukis
Copy link

Also updated the specs since they were issuing deprecation warnings.

@@ -7,14 +7,15 @@
it 'can describe an index that returns ids for the class type' do
test_index = clazz.cloudsearch_index
test_index.should be_kind_of(Cloudsearchable::Domain)
test_index.fields.should have(4).items #3 explicit + 1 for the id of the object
# test_index.fields.should have(4).items #3 explicit + 1 for the id of the object
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you move the comment to the new line, and remove the commented-out line of code?

Copy link
Author

Choose a reason for hiding this comment

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

Missed this comment. Sorry, I have removed the comment. I didn't mean to commit with the comment. I only had it during testing the change as reference.

@philipmw
Copy link
Contributor

philipmw commented Oct 9, 2015

Yehuda Katz suggests that libraries should not have Gemfile.lock in revision control. His argument makes sense to me. Can you either remove it, or explain why we want it?

@chriskaukis
Copy link
Author

I had not seen that, but I just read over it and it makes sense. I have removed the Gemfile.lock file.

@philipmw
Copy link
Contributor

Would you squash these three commits into one?

@philipmw
Copy link
Contributor

Another contributor merged this functionality. So I'm closing this PR. Thanks for your contribution.

@philipmw philipmw closed this Nov 13, 2015
@chriskaukis
Copy link
Author

Oh, I'm sorry. I completely forgot to squash the commits like you asked. My apologies. Thank you!

@rmpugh
Copy link

rmpugh commented Dec 11, 2015

Just wondering about this PR - it was getting somewhere to support the new API version (2013), but the other PR did not do this. Are there any plans to update to the new API version?

@philipmw
Copy link
Contributor

I see what you're saying. In addition to updating the SDK gem to v2, you're also using the newer API version. Someone else's PR also updated the SDK gem to v2, so I prematurely closed your PR thinking that it duplicates the functionality. Sorry. Please let's finish the work of using the newer API!

@philipmw philipmw reopened this Dec 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants