8000 Wire deserialisation does not set resourceSetName · Issue #158 · Algo-Web/POData · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Wire deserialisation does not set resourceSetName #158

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our A06A terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
CyberiaResurrection opened this issue Aug 25, 2017 · 1 comment
Open

Wire deserialisation does not set resourceSetName #158

CyberiaResurrection opened this issue Aug 25, 2017 · 1 comment
Assignees
@CyberiaResurrection @c-harris
Labels
hacktoberfest help wanted

Comments

@CyberiaResurrection
Copy link
Collaborator

The resourceSetName property in deserialised ODataEntry objects must point to a ResourceSet, otherwise the cynic deserialiser doesn't know what properties it should be expecting, etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CyberiaResurrection CyberiaResurrection

@c-harris c-harris

Labels
hacktoberfest help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CyberiaResurrection and others
0