-
Notifications
You must be signed in to change notification settings - Fork 39
Improve Join Condition Parsing for Complex Queries #69
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
base: master
Are you sure you want to change the base?
Conversation
Improve Join Condition Parsing for Complex Queries
Code litting
|
@ZaidMaslouhi I struggle to understand what is the point of this? There are two places where you change something that is configurable with hardcoded value . What is the purpose of that? |
|
@zaro Thank you for the feedback.
The goal is to solve the array parsing issue while maintaining the library's flexibility. |
Add array delimiter to the request query builder options config
|
Hi dudes, I'm building a rest api using nest js and this fantastic framework, but now I don't know how to stablish some relations, can you help me please? |
|
Hello @ccasado16, I suggest that you review the documentation. It covers all the necessary information to create a Rest API using NestJS |
i need the help of a expert because there are some things i don't understand at all |
|
@ccasado16 You can contact me over email : zarrro AT gmail DOT com , and provide mode details what do you need help with. |
|
great, I already wrote you a message @zaro |
Description
Enhance the join condition parsing mechanism to support more complex query scenarios, particularly those involving array-like values such as date ranges.
Key Changes
Detailed Improvements
Parsing Mechanism
Testing
Documentation
Example Usage
Impact
Related Issues
Closes #68 (if applicable)
Type of Changes
Testing