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

Hide IBMWatsonMapModel object from the outside #74

Open
2 tasks
lpatino10 opened this issue Feb 13, 2018 · 0 comments
Open
2 tasks

Hide IBMWatsonMapModel object from the outside #74

lpatino10 opened this issue Feb 13, 2018 · 0 comments

Comments

@lpatino10
Copy link
Contributor

Internally, any properties that would be of type Map<String, Object> use the wrapper model IBMWatsonMapModel because the base Apex deserializer doesn't support the former.

However, from a developer's perspective, they should be able to set properties that would be of type Map<String, Object> by using the standard Map. It's awkward to have to use an SDK-specific type and prevents things like inline initialization.

Acceptance Criteria:

  • Developers are able to set Map parameters using the standard datatype
  • Models are still properly serialized/deserialized internally
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant