The macro is currently hardcoded to superitem. Two main problems:
it doesn't allow multiple OrderedRelationship macros to point to the same SubItem model class,
it doesn't work well if superitem doesn't describe the containing class well.
This PR also fixes a bug around containingClassName: the current implementation doesn't use the label, it just uses the first argument, even if that argument is one of the other labeled args.
I've added some tests around existing functionality and the new inverseRelationshipName
The macro is currently hardcoded to
superitem. Two main problems:superitemdoesn't describe the containing class well.This PR also fixes a bug around
containingClassName: the current implementation doesn't use the label, it just uses the first argument, even if that argument is one of the other labeled args.I've added some tests around existing functionality and the new
inverseRelationshipName