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.

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

[WIP] Special behaviour for temporal prefixes #1644

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

THardy98
Copy link
Contributor

@THardy98 THardy98 commented Mar 11, 2025

What was changed

Special behavior handling reserved temporal prefixes. Prevent users from:

  • registering workflows, activities, task queues, signals/updates/queries with a reserved prefix
  • calling default handlers with reserved names
  • calling internal queries without going through interceptors

This change makes the reserved metrics names reserved across all entities (workflows, activities, signals, etc..).


Checklist

Some remaining items:

  • test for default signal handler & reserved names needs to be fixed
  • need to reserving prefixes from workflows,
  • waiting for default update handler to be merged to prevent default update handler to be called with reserved names
  1. Closes [Feature Request] Special behavior for Temporal built-in prefixes #1599

  2. How was this tested:
    unit/integration tests

  3. Any docs updates needed?
    I'm not sure.

… test needs to be fixed, need to add behaviour reserving prefixes from workflows, and waiting for default update to be merged to add behaviour preventing default update handler to be called with reserved names
@THardy98 THardy98 requested a review from a team as a code owner March 11, 2025 02:12
@THardy98
Copy link
Contributor Author

In this change, users are prevented from registering signals/updates/queries with reserved names from the handler.

Users can still defineQuery, defineSignal, defineUpdate that have reserved names. The reason for this is because we use defineQuery to create the reserved queries ourselves.

Alternatively, we can do the blocking in define<X> and create our internal queries/signals/updates using internal functions. Or we can do both (blocking in the define and the handler). I picked one because it seemed sufficient.

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.

[Feature Request] Special behavior for Temporal built-in prefixes
1 participant