Skip to content

Keep the deferred choice out of the exposed node set for now - #144

Merged
noha merged 1 commit into
mainfrom
hide-deferred-choice
Sep 10, 2026
Merged

noha merged 1 commit into
mainfrom
hide-deferred-choice

Conversation

@noha

@noha noha commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

ApptiveGrid lists every non-abstract node class to its client as a type a user can pick, and the client knows nothing of a deferred choice yet. FBDeferredChoice reads abstract in that sense, like FBRemoteFlowTask and FBTerminateEvent, and stays instantiable; an ApptiveBase subclass lifts this once the client can show and configure one.

ApptiveGrid lists every non-abstract node class to its client as a type
a user can pick, and the client knows nothing of a deferred choice yet.
FBDeferredChoice reads abstract in that sense, like FBRemoteFlowTask
and FBTerminateEvent, and stays instantiable; an ApptiveBase subclass
lifts this once the client can show and configure one.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@noha
noha merged commit d91af0a into main Sep 10, 2026
4 checks passed
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.

1 participant