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
{{ message }}
This repository has been archived by the owner on May 11, 2021. It is now read-only.
I have commented on this i think, but just in case - we can't move this into __render_where, because the wrapping methods would typically prepend " having", " where" and if there are no clauses at all, we should return null, that's why this check is done on the top-level.
Yeah, but I've read in the code developer guidelines to return from methods early if possible.
It's not a huge deal really. Plus all of the _render() methods have the same code to return 'null' if their presence is not needed. Perhaps we can even move it to render() method, but I'm not sure at this time if it can create more problems or not.
This piece of code is found in
_render_where
,_render_orwhere
,_render_andwhere
,_render_having
:It can me moved to
__render_where
method to not duplicate code:and in previously mentioned methods do simply like this:
The text was updated successfully, but these errors were encountered: