Skip to content

[Java] Breaking change for timeout parameters for SocketSettings builder methods #519

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

Closed
wants to merge 16 commits into from

Conversation

rachel-mack
Copy link
Contributor

@rachel-mack rachel-mack commented Jan 29, 2024

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-35763
Staging

This includes a few weird changes that are artifacts from a rebase.

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Did you run a spell-check?
  • Did you run a grammar-check?
  • Are all the links working?
  • Are the facets and meta keywords accurate?

@rachel-mack rachel-mack marked this pull request as ready for review January 30, 2024 19:41
Copy link
Contributor

@jordan-smith721 jordan-smith721 left a comment

Choose a reason for hiding this comment

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

Just a couple small suggestions

Comment on lines 70 to 71
- The first parameter, time durations, of the following ``SocketSettings``
builder methods is of ``long`` type:
Copy link
Contributor

Choose a reason for hiding this comment

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

Q: is the first parameter called "time durations"? If so I would monospace it (and I'm assuming camel-case it). I think being more specific with it will be more helpful.

Also I think we could be more concise here by just saying:

Suggested change
- The first parameter, time durations, of the following ``SocketSettings``
builder methods is of ``long`` type:
- The time durations parameter of the following ``SocketSettings``
builder methods is of ``long`` type:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The parameter names are connectTimeout and readTimeout, which is the first parameter of each. I've changed to your phrasing and changed it to "timeout", but have not monospaced it. I think it should be clear this way to anyone who's using either method.

Comment on lines 114 to 115
guide. This change breaks binary compatibility (requires recompiling) but does not
require code changes.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion: I think we generally try to avoid putting statements in parenthesis like this if not necessary.

Suggested change
guide. This change breaks binary compatibility (requires recompiling) but does not
require code changes.
guide. This change breaks binary compatibility and requires recompiling, but does not
require code changes.

Copy link
Contributor

@jordan-smith721 jordan-smith721 left a comment

Choose a reason for hiding this comment

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

LGTM w/ one change!

Comment on lines +70 to +71
- The timeout parameters of the following ``SocketSettings``
builder methods is of ``long`` type:
Copy link
Contributor

Choose a reason for hiding this comment

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

S: make parameters singular so it doesn't read like it's multiple for each one

Suggested change
- The timeout parameters of the following ``SocketSettings``
builder methods is of ``long`` type:
- The timeout parameter of the following ``SocketSettings``
builder methods is of ``long`` type:

@rachel-mack rachel-mack requested a review from stIncMale January 30, 2024 21:00
Copy link
Member

@stIncMale stIncMale left a comment

Choose a reason for hiding this comment

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

The PR description states that this PR documents https://jira.mongodb.org/browse/DOCSP-35763, which is a duplicate of https://jira.mongodb.org/browse/DOCSP-34994 (I wonder, why it was created). And the latter has already been reviewed as part pf #507.

Moreover, I see many changes unrelated to https://jira.mongodb.org/browse/DOCSP-35763 in this PR. Why are they here?

I'll wait until this PR gets well-organized/tidied up before proceeding with reviewing it. However, as far as I can see, all the changes here must have been already documented in other PRs, and this PR should probably be just closed.

@rachel-mack
Copy link
Contributor Author

The PR description states that this PR documents https://jira.mongodb.org/browse/DOCSP-35763, which is a duplicate of https://jira.mongodb.org/browse/DOCSP-34994 (I wonder, why it was created). And the latter has already been reviewed as part pf #507.

You're right - this is a duplicate and I'll remove it.

@rachel-mack rachel-mack closed this Feb 8, 2024
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.

3 participants