Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Special behavior for Temporal built-in prefixes #576

Open
2 of 9 tasks
cretz opened this issue Jan 14, 2025 · 0 comments
Open
2 of 9 tasks

Special behavior for Temporal built-in prefixes #576

cretz opened this issue Jan 14, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@cretz
Copy link
Member

cretz commented Jan 14, 2025 •
edited by josh-berry
Loading

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)

Per-SDK Tickets
@cretz cretz added the enhancement New feature or request label Jan 14, 2025
@cretz cretz changed the title Special behavior for Temporal built-in queries Special behavior for Temporal built-in handlers Jan 14, 2025
@cretz cretz changed the title Special behavior for Temporal built-in handlers Special behavior for Temporal built-in prefixes Jan 14, 2025
This was referenced Jan 15, 2025
Open
Open
Open
Open
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cretz