Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

(5 of 5) Remove deprecated disableTransactions methods from ClientWriteOptions (breaking, major bump)

Open
#370 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java
Domain
api

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) and disableTransactions().
  • Collapse any internal plumbing that only existed to bridge the old and new field representations, so transactionsEnabled is 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 disableTransactions remain 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) to transactions(false), disableTransactions(false) to transactions(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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openfga/java-sdk

All issues in openfga/java-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.