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

Deprecate activate_always/activate_on #16

Open
palkan opened this issue Feb 2, 2023 · 0 comments
Open

Deprecate activate_always/activate_on #16

palkan opened this issue Feb 2, 2023 · 0 comments
Assignees
@palkan
Labels
enhancement New feature or request

Comments

@palkan
Copy link
Owner

palkan commented Feb 2, 2023

Is your feature request related to a problem? Please describe.

Adding activate_always / activate_on is boring, we can do better.

Describe the solution you'd like

We can rely on block signature to infer activation rules:

  • if all kwrags have default values -> activate always
  • if some kwargs have default values -> active on these keys
@palkan palkan added the enhancement New feature or request label Feb 2, 2023
@palkan palkan self-assigned this Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@palkan palkan

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@palkan