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 Apr 20, 2024. It is now read-only.
Since we're already annotating relations, I think it makes sense to have Sourcery create relations. E.g. in the case of (inside Employee.swift):
// sourcery: preparation = foreignId, unique = false, foreignTable = Company
internal var companyId: Identifier?
Then it could create an extension on Employee with a property called company which would return the parent. Similarly it could create an extension on Company with a property called employees which would return the children.
We could consider if it makes sense to have an annotation to indicate 1-1 relations so instead of returning all the children it would return the first children.
The text was updated successfully, but these errors were encountered:
Currently you're able to annotate your struct/class with ignoreJSONConvertible to avoid the JSONConvertible extension being created. Further you can annotate with ignoreJSONConvertible on your properties to exclude specific properties from the JSONConvertible extension.
Is this what you need?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since we're already annotating relations, I think it makes sense to have Sourcery create relations. E.g. in the case of (inside
Employee.swift
):Then it could create an extension on
Employee
with a property calledcompany
which would return the parent. Similarly it could create an extension onCompany
with a property calledemployees
which would return the children.We could consider if it makes sense to have an annotation to indicate 1-1 relations so instead of returning all the children it would return the first children.
The text was updated successfully, but these errors were encountered: