-
-
Notifications
You must be signed in to change notification settings - Fork 52
Description
Look at the two following PRs to get copilot-setup-steps.yml
& .copilot/instructions.md
setup.
#1890
#1888
We have a limitation at the moment where users are not able to match on null values which I'd like to fix. We only allow them to compare numbers, strings, dates & arrays currently.
This is further complicated by the fact we return null for missing data, as well as when exceptions occur. For clarity, null should be returned for missing data only, so that we can match it with this new functionality, we should return some kind of error for exceptions. This PR has an implementation for returning an error for the execution which would be useful here. This PR should also be integrated as it fixes a bug related to this feature.
I'd like for you to explore several solutions to this problem, and then explain them in great detail. The solutions should:
- Be user friendly
- Try and be as simple as possible on the backend
- Backwards compatible for users existing rule groups (where possible - please explain impact otherwise)
We may want to update some of the API response types to include null
to improve type safety here, here's docs for each service:
- Sonarr: OpenAPI Specification
- Radarr: OpenAPI Specification
- Tautulli: API Reference Documentation
- Overseerr: API Documentation
- Jellyseerr: OpenAPI Specification
- Plex: OpenAPI Specification | Additional Documentation