"Accessory checkout" version of checkout accessories to locations #15306
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For being able to 'checkout to ___location' as well as 'checkout to user' for Accessories, a lot of the fundamentals of how those relationships work needs to change. This is one attempt at getting those relationships to sort-of work right.
At this point, I can go into Tinker and, from an Accessory, look at AccessoryCheckouts which can point to users or locations. As well as going the other directions.
The extra level of indirection is a little awkward when running through the relationships, which is why I figured MorphedByMany approach might be better - but, in fact, it's so much worse :(
This is by no means complete, but at least the basic relationships seem to work at the model level.