Problem Description:
When utilizing the repository and its functions, there is a recurring issue of encountering overly long and deeply nested queries, rendering the library practically unusable. This problem seems to arise particularly when using generics.
Issue Inquiry:
I'm unsure if the observed behavior is intended, or if I'm misunderstanding the library's usage. Specifically, I'm uncertain whether utilizing generics in this context is supported and if there's a mistake in my implementation.
Additional Context:
While I'm very happy with this library and it essentially provides exactly what I've been searching for, the extensive nesting and complexity hinder the library's usability, particularly when dealing with generics. Understanding the intended behavior would greatly assist in resolving these challenges and effectively leveraging the library's functionality.
Thank you for your attention to this matter. Any guidance or clarification would be greatly appreciated.
Hi, first of all: Thanks for this amazing tool!!
Problem Description: When utilizing the repository and its functions, there is a recurring issue of encountering overly long and deeply nested queries, rendering the library practically unusable. This problem seems to arise particularly when using generics.
Small simple Example:
Issue Inquiry: I'm unsure if the observed behavior is intended, or if I'm misunderstanding the library's usage. Specifically, I'm uncertain whether utilizing generics in this context is supported and if there's a mistake in my implementation.
Additional Context: While I'm very happy with this library and it essentially provides exactly what I've been searching for, the extensive nesting and complexity hinder the library's usability, particularly when dealing with generics. Understanding the intended behavior would greatly assist in resolving these challenges and effectively leveraging the library's functionality.
Thank you for your attention to this matter. Any guidance or clarification would be greatly appreciated.