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

Support behavioral dependencies #92

Open
handrews opened this issue Apr 10, 2023 · 0 comments
Open

Support behavioral dependencies #92

handrews opened this issue Apr 10, 2023 · 0 comments

Comments

@handrews
Copy link
Contributor

Currently, keywords can only depend on specific other keywords. However, the specification (particularly the unevaluated* keywords) requires depending on in-place applicators as a behavioral class. If a custom in-place applicator is used, it is expected to automatically affect unevaluated*.

This requires marking the behavior and also sorting dependencies accordingly.

Behavior marking could be done with a base class or mixin, but given other architectural decisions in this project, it seems more appropriate to use class attributes similar ot the existing depends_on and instance_types attributes.

The only behavior that currently needs this support is in-place application. I would be disinclined to add further behaviors without use cases, but the mechanism should work for any future behavior should the need arise.

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

No branches or pull requests

1 participant