-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
reuse repo in repo #255
Comments
I tried to reproduce it and I didn't have a problem. Perhaps, the relation here It should be fine as long as |
@bingtsingw please give more details on this issue (ideally, a repro). I just pushed update related to joins, maybe it's fixed, then confirm please if this is still relevant, or let's close. |
@romeerez Sorry for the late response, I'm a little busy these days, I'll make a reproduce repo may be next week. |
And I found this fixed issue (#242) breaks in the |
No problem, take your time. I ran the test for 242 and it passed, there are type errors in the test suite, but it doesn't seem to be a bug in ORM. await dr.activityMember
.whereByUserVipTo('>', new Date())
.whereByUserVipTo('<', addDays(new Date(), 5))
.select('id', 'user.id'); Here return query.leftJoin('user');
// instead of:
return isJoinUser ? query : query.leftJoin('user'); And later there is a type error here: query = query.whereByUserVipTo(... The type doesn't match, but it doesn't have to match, it doesn't seem to be a problem. |
In issue #244, this works:
But when reuse myRepo in another repo, it does not work
The text was updated successfully, but these errors were encountered: