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
Right now we cannot create two schemas that both have references to each other. This is a variant of the issue #35.
I need to have two schemas, one for an Organization and one for a Member. So the code I wrote is this:
The MemberSchema used in the definition of OrganizationSchema does not get recognized by typescript as it is not yet defined at that point.
Trying something like the workaround in issue #35 causes an issue in populateTs() where the populated items don't have the added properties. Also, I highly dislike the redundant type of code used for this workaround.
It would be great if you can fix this issue! Thanks!
The text was updated successfully, but these errors were encountered:
Did you find a better workaround, or is the workaround in #35 the only way to go? One problem I have been facing is circular dependencies since if I split the schemas out into 2 different files the imports get messed up.
Right now we cannot create two schemas that both have references to each other. This is a variant of the issue #35.
I need to have two schemas, one for an Organization and one for a Member. So the code I wrote is this:
The
MemberSchema
used in the definition ofOrganizationSchema
does not get recognized by typescript as it is not yet defined at that point.Trying something like the workaround in issue #35 causes an issue in
populateTs()
where the populated items don't have the added properties. Also, I highly dislike the redundant type of code used for this workaround.It would be great if you can fix this issue! Thanks!
The text was updated successfully, but these errors were encountered: