(5 of 5) Remove deprecated disableTransactions methods from ClientWriteOptions (breaking, major bump)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start in src/main/java/dev/openfga/sdk/api/configuration/ClientWriteOptions.java, then search java-sdk source, tests, examples, generated README, sdk-generator Java templates, and spring-boot-starter examples for disableTransactions references. Confirm the deprecation has shipped, a full release cycle has passed, and the next release is a major bump; done means references are removed, the back-compat test is gone, and the CHANGELOG and release communications include the breaking-change migration note.
Written by the indexing model from the issue text.
Description
Context
ClientWriteOptions.disableTransactions(boolean) and disableTransactions() are the double-negative predecessors of transactions(boolean) and isTransactionsEnabled() (added in PR #352). Once they have been deprecated and users have had a release cycle to migrate, they should be removed.
Removing public methods is a breaking change and must land in a major version bump.
Preconditions
- The deprecation issue has shipped in a release.
- At least one full release cycle has passed so consumers had a deprecated-but-present window to migrate.
- The next release is a major version bump.
Scope
src/main/java/dev/openfga/sdk/api/configuration/ClientWriteOptions.java:
- Remove
disableTransactions(boolean)anddisableTransactions(). - Collapse any internal plumbing that only existed to bridge the old and new field representations, so
transactionsEnabledis the single source of truth. - Remove the back-compat test kept in the deprecation issue.
Verify no remaining references across the org before removal: java-sdk (src, tests, examples, README), sdk-generator Java templates, spring-boot-starter examples.
Acceptance criteria
- No references to
disableTransactionsremain in java-sdk source, tests, examples, or generated README. - Release is versioned as a major bump.
- CHANGELOG documents the removal as a breaking change with the migration mapping (
disableTransactions(true)totransactions(false),disableTransactions(false)totransactions(true),disableTransactions()to!isTransactionsEnabled()). - A migration note is included in release communications.
Sequencing
Step 4, final. Blocked by the deprecation issue and a release-cycle wait. Tracked in the umbrella issue.
Owner: @curfew-marathon
- Dominant language
- Java
- Stars
- 54
- Forks
- 26
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openfga/java-sdk
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement needs-discussion
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in openfga/java-sdk
Similar issues
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
integra-team-red/meet-map#249 ·
-
[Studio][Bug] Cancelled create-user dialog keeps the password and admin switch for the next attempt Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/rocketmq-dashboard#5064 ·