temporalio / temporalio/features

Special behavior for Temporal built-in prefixes

Open
#576 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
32
Forks
28
Avg merge
1d 9h
Merged PRs (30d)
7

Description

Describe the solution you'd like

All SDKs need to do the following:

  • Disallow workflows, activities, Nexus operations/services, task queues, signals, queries, and updates to be registered that start with __temporal_
  • Disallow queries to be registered that equal __stack_trace or __enhanced_stack_trace
  • Do not call dynamic handlers with reserved names
  • For any query that does match the above pattern, it should be handled without going through interceptors (this means that it no longer appears in tracing for instance) [should apply to everything except Go/Java]
Per-SDK Tickets

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the remaining TypeScript issue #1599 and Python issue #731, then compare them with the completed per-SDK tickets listed here. Done means the applicable SDKs enforce the reserved-name registration and dynamic-handler rules and handle matching queries without interceptors where specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, go, java, php, python, ruby, typescript
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.