We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
core.py
We should implement support for non-core.py rulebases in PREP. There are several TODOs in the code for this, but I don't see an open issue.
TODO
The text was updated successfully, but these errors were encountered:
core.py has proven enough of a jumping off point...
and with only one way to do things... it's fewer configuration options to hold poorly.
so yes, if nothing else, we can remove the TODOs.
Sorry, something went wrong.
Ah, if there are multiple instances... each instance could load a separate .py module.
But I think we should limit the config to only allow one file per instance... and still core.py if empty/undefined so it remains backwards compatible.
No branches or pull requests
We should implement support for non-
core.py
rulebases in PREP. There are severalTODO
s in the code for this, but I don't see an open issue.The text was updated successfully, but these errors were encountered: