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

ideas for extending the patch YAML system #504

Open
4 of 7 tasks
beckermr opened this issue Aug 17, 2023 · 0 comments
Open
4 of 7 tasks

ideas for extending the patch YAML system #504

beckermr opened this issue Aug 17, 2023 · 0 comments

Comments

@beckermr
Copy link
Member

beckermr commented Aug 17, 2023

Here are some ideas for extending the patch YAML system:

  • enable logical negation for the if conditions (i.e., the Python equivalent of not ...) (ENH enable negation #510)
  • enable an outer list if syntax where the inner items are dicts (entries are combined via AND) and the outer list items are combined via OR. (can use another template instead)
  • add a required comment field in the pydantic model so that we can keep the reasons for the patches machine-readable
  • add a debug field per-patch that would output info as the patch is applied/tested to help people figure out why a patch was not working (this would need to have its own set of conditions so that it didn't print gobs of text)
  • add input data that could be referenced
  • support referencing current record values via string.Template with $ syntax. (ENH allow template strings #513)
  • add support for has_constrains in if section (ENH support has constrains #512)

cc @jaimergp

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