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 Map.update bug in Deserializer #7

Closed

Conversation

micahwedemeyer
Copy link
Collaborator

[fixes #6]

@zabirauf
Copy link
Owner

zabirauf commented Jan 9, 2017

If the outcome is completely deprecated then we need to update the model accordingly as well and increase the major version number as its a contract change.

@micahwedemeyer
Copy link
Collaborator Author

I'll look into it, but my main concern is that a version change probably has repercussions across all the request endpoints: message, converse, and so on.

Perhaps as a step 1, we merge this PR, and step 2 is to branch and begin updating everything to the latest version.

@micahwedemeyer
Copy link
Collaborator Author

I'm going to close this request and open another one that represents a full update to the current Wit API.

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.

function Map.update/3 is undefined or private in Wit.Client.Deserializer
2 participants