8000 V8 rc1 by lpatino10 · Pull Request #1082 · watson-developer-cloud/java-sdk · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@lpatino10
Copy link
Contributor

This PR generates everything fresh for the v8.0.0 pre-release. This is using the following commits:

API def: 9ee9439cbe050c75137dc0d3ea9db03633cd505c
Generator: c3d3873bf9046b43710702c216646be9af736ac8

Most changes are related to authorization config changes and the addition of builders on all of the request models that were missing them previously. All documentation has been updated to reflect big user-facing changes.

@lpatino10
Copy link
Contributor Author

Taj, just a note: I went ahead and disabled semantic-release on CI for this. I wasn't too sure how it and bumpversion would handle the new version syntax. I'll push a tag manually once this is merged to kick off the release process with Bintray.

@codecov-io
Copy link
codecov-io commented Aug 28, 2019

Codecov Report

Merging #1082 into 8.0.0-rc will decrease coverage by 4.24%.
The diff coverage is 47.91%.

Impacted file tree graph

@@              Coverage Diff               @@
##             8.0.0-rc    #1082      +/-   ##
==============================================
- Coverage       69.77%   65.53%   -4.25%     
+ Complexity       3190     3002     -188     
==============================================
  Files             650      652       +2     
  Lines           15588    17099    +1511     
  Branches          903      934      +31     
==============================================
+ Hits            10877    11205     +328     
- Misses           4323     5528    +1205     
+ Partials          388      366      -22
Impacted Files Coverage Δ Complexity Δ
...ery/v1/model/GetMetricsQueryTokenEventOptions.java 69.23% <ø> (ø) 2 <0> (ø) ⬇️
...java/com/ibm/watson/discovery/v1/model/Filter.java 100% <ø> (ø) 2 <0> (ø) ⬇️
...ibm/watson/discovery/v1/model/QueryLogOptions.java 73.68% <ø> (ø) 6 <0> (ø) ⬇️
...on/discovery/v1/model/ListTrainingDataOptions.java 54.16% <ø> (ø) 3 <0> (ø) ⬇️
...com/ibm/watson/discovery/v1/model/GatewayList.java 100% <ø> (ø) 2 <0> (ø) ⬇️
...son/discovery/v1/model/GetTrainingDataOptions.java 54.83% <ø> (ø) 4 <0> (ø) ⬇️
...atson/discovery/v1/model/QueryEntitiesContext.java 0% <ø> (ø) 0 <0> (ø) ⬇️
.../watson/assistant/v2/model/DialogNodesVisited.java 100% <ø> (ø) 4 <0> (ø) ⬇️
...n/discovery/v1/model/ListEnvironmentsResponse.java 100% <ø> (ø) 2 <0> (ø) ⬇️
...iscovery/v1/model/DeleteConfigurationResponse.java 100% <ø> (ø) 4 <0> (ø) ⬇️
... and 475 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 31a23f4...b667b16. Read the comment docs.

Copy link
Contributor
@mediumTaj mediumTaj left a comment

Choose a reason for hiding this comment

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

👍 looks good! I just had a few questions but approving since nothing particularly important.

```

#### ICP
#### Cloud Pak for Data
Copy link
Contributor

Choose a reason for hiding this comment

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

Looking at this I wonder if we need to keep an example for ICP authentication. This would be using BasicAuthenticator and disabling ssl verification. What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah that might be worth it. I don't know the numbers on people using the SDKs on ICP but it's probably similar to CP4D so it can't hurt 🤷‍♀

private DeleteIntentOptions(Builder builder) {
Validator.notEmpty(builder.workspaceId, "workspaceId cannot be empty");
Validator.notEmpty(builder.intent, "intent cannot be empty");
com.ibm.cloud.sdk.core.util.Validator.notEmpty(builder.workspaceId,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any reason why you changed to use the full namespace for Validator?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, this started in this issue, which then became this PR.

There was some discussion in there that some internally-used classes like Validator should be fully-qualified for future-proofing against any possible conflicts with generated code. This specific change was added (among other things) here.

@@ -21,16 +21,16 @@
public class Class extends GenericModel {

@SerializedName("class")
private String className;
private String xclass;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a java naming convention?

Copy link
Contributor Author

Choose a reason for hiding this c 7440 omment

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

Not really... I wasn't too sure about what to do with the reserved names and there's no set Java convention.

I think it'll be better at least to just keep the x and camelCase the name. I'll make that change.

@@ -64,7 +64,7 @@ checkstyle {
dependencies {
compile project(':common')
testCompile project(':common').sourceSets.test.output
compile 'com.ibm.cloud:sdk-core:4.5.0'
compile 'com.ibm.cloud:sdk-core:7.0.0-rc1'
Copy link
Contributor

Choose a reason for hiding this comment

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

Did the core jump from 4.x.x to 7.x.x?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Surprisingly, yes 😬

@lpatino10 lpatino10 merged commit 53ea7db into 8.0.0-rc Aug 29, 2019
@lpatino10 lpatino10 deleted the v8-rc1 branch August 29, 2019 17:01
@watson-github-bot
Copy link
Contributor

🎉 This PR is included in version 8.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants

0