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
autobind is a great addition, but I have models that don't always match the type name 1:1.
It'd be useful to augment autobind with a path prefix, which could then be used as a starting point to find a model using the regular <package>.<model> designation, e.g.
Ultimately, my goal is to move this config to schema files and avoid hard-coding absolute package paths for each definition / repeating the same prefix:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Proposal:
autobind
is a great addition, but I have models that don't always match the type name 1:1.It'd be useful to augment autobind with a path prefix, which could then be used as a starting point to find a model using the regular
<package>.<model>
designation, e.g.Ultimately, my goal is to move this config to schema files and avoid hard-coding absolute package paths for each definition / repeating the same prefix:
The text was updated successfully, but these errors were encountered: