Repository navigation
docs(release-notes): Document Context null-safety change in 2.2 - #234
Merged
Merged
Conversation
Context.getProcessEngineConfiguration() and Context.getCommandContext() throw IllegalStateException in 2.2 instead of returning null when no command is active. Document the change, the new find*/hasActive* alternatives, and recommend public service APIs instead. Related to operaton/operaton#4038 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
A maintainer must confirm or remove the unverified Operaton 2.3 commitment to internal-package declarations and stricter enforcement before publication.
No open issues 🎉
What changed in this PR
Documents the internal Context null-safety change in Operaton 2.2 and provides migration guidance for applications that previously relied on nullable getters.
Changes:
- Describes the new exceptions, optional-returning alternatives, and context-presence checks.
- Adds migration examples, recommends public APIs, and warns about internal API stability.
- Updates the nullability section to acknowledge the behavior change and link to the new guidance.
| File | Description |
|---|---|
docs/documentation/reference/release-notes/2_2/index.md |
Adds Context migration guidance and internal API warnings; corrects the nullability overview. |
Review effort: Balanced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents an internal API change in the 2.2 release notes that was missing, as promised in operaton/operaton#4038 (comment).
Since 2.2 (operaton/operaton#3550),
Context.getProcessEngineConfiguration()andContext.getCommandContext()throw anIllegalStateExceptioninstead of returningnullwhen no engine command is active on the current thread.Changes in
release-notes/2_2/index.md:findProcessEngineConfiguration()/hasActiveProcessEngineConfiguration()/findCommandContext()/hasActiveCommandContext()methods, with a migration exampleRuntimeService,DelegateExecution, ...) instead of internalContext.impl.packagesOpen point
The warning box states plans for 2.3 (explicit declaration of internal packages, stricter enforcement). Please confirm or drop before merging.
Test plan
npm run buildsucceeds; no broken links/anchors reported for release notes pages#context-null-safetyanchor renders🤖 Generated with Claude Code