Skip to content

Conversation

tanmayb123
Copy link
Contributor

Some developers (like me) prefer JSON over XML, and the relationship extraction API does not allow users to choose their preferred return type.

@codecov-io
Copy link

Current coverage is 24.70%

Merging #185 into dev will decrease coverage by -26.53% as of e589268

@@              dev   #185   diff @@
====================================
  Files         208     63    -145
  Stmts        4124   2133   -1991
  Branches      431    395     -36
  Methods         0      0        
====================================
- Hit          2113    527   -1586
+ Partial       235     98    -137
+ Missed       1776   1508    -268

Review entire Coverage Diff as of e589268

Powered by Codecov. Updated on successful CI builds.

*
* @param returnType the new returnType
*/
public void setReturnType(final REReturnType returnType) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please don't use acronyms. ReturnType is fine.

@germanattanasio
Copy link
Contributor

This is looking really good!

@tanmayb123
Copy link
Contributor Author

Thanks! And I've removed the RE acronym from REReturnType.

germanattanasio added a commit that referenced this pull request Feb 9, 2016
Option for "Return Type" to be JSON in Relationship Extraction
@germanattanasio germanattanasio merged commit c321fd3 into watson-developer-cloud:dev Feb 9, 2016
@germanattanasio
Copy link
Contributor

Thanks!

@germanattanasio germanattanasio mentioned this pull request Feb 9, 2016
@tanmayb123 tanmayb123 deleted the dev branch February 9, 2016 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants