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

Wrapped the contract after user-adjustable settings #705

Merged
merged 1 commit into from
Jun 10, 2014

Conversation

bytenik
Copy link
Contributor

@bytenik bytenik commented Jun 7, 2014

No description provided.

@Mpdreamz
Copy link
Member

Thank you for looking into this @bytenik and coming up with an easy solution for #701.

@Mpdreamz Mpdreamz closed this Jun 10, 2014
@Mpdreamz Mpdreamz reopened this Jun 10, 2014
Mpdreamz added a commit that referenced this pull request Jun 10, 2014
Wrapped the contract after user-adjustable settings
@Mpdreamz Mpdreamz merged commit b66008f into elastic:master Jun 10, 2014
@bytenik bytenik deleted the wrapped-contract branch June 13, 2014 17:41
@jimsorock
Copy link

@Mpdreamz @bytenik is there an example on how to use/override this contract resolver?

@bytenik
Copy link
Contributor Author

bytenik commented Jun 10, 2015

@jimsorock What do you mean? What are you trying to accomplish?

@jimsorock
Copy link

Trying to replace the contract resolver. I know when setting up the client that I can add json converters, but I was wondering how this fixed the issue in #701.

@bytenik
Copy link
Contributor Author

bytenik commented Jun 10, 2015

You can replace the resolver with one that passes through requests for contracts for a NEST type to a NEST resolver.

@jimsorock
Copy link

Ok but where does that replace actually happen? Do I just subclass my own contract resolver from the new SettingsContractResolver?

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.

3 participants