You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
The focus here is on ensuring that filters exist for the prompts and/or payloads of all features, are standardized to a reliable format (e.g., classifai_{feature}_{service}_prompt), and that any pre-existing filters that need to be standardized are updated/deprecated accordingly (e.g. soft deprecation in one major release, hard deprecated in a subsequent major release). This will allow for reliable filters regardless of feature and service provider and that ClassifAI’s Developer Documentation becomes easier to read and understand.
The potential approach to working on this could be:
Go through the plugin and make a note of all hooks (probably pull these into a Google Sheet)
During this process, make a note of any places that are missing hooks that would benefit from having one added
Once done, we can have a conversation on which hooks we should add and which of the existing hooks should be renamed
After all this, the actual work can be done
Designs
n/a
Describe alternatives you've considered
n/a
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem? Please describe.
The focus here is on ensuring that filters exist for the prompts and/or payloads of all features, are standardized to a reliable format (e.g., classifai_{feature}_{service}_prompt), and that any pre-existing filters that need to be standardized are updated/deprecated accordingly (e.g. soft deprecation in one major release, hard deprecated in a subsequent major release). This will allow for reliable filters regardless of feature and service provider and that ClassifAI’s Developer Documentation becomes easier to read and understand.
The potential approach to working on this could be:
Designs
n/a
Describe alternatives you've considered
n/a
Code of Conduct
The text was updated successfully, but these errors were encountered: