The ResourceMetaClass currently handles the relationships between resources. It would be better for a multitude of reasons including the removal of the dumb as hell meta class that currently manages them and the included ability of independently managing api versions (you would be able to independently set the base url, e.g. "apiv1" or "apiv2").
The ResourceMetaClass currently handles the relationships between resources. It would be better for a multitude of reasons including the removal of the dumb as hell meta class that currently manages them and the included ability of independently managing api versions (you would be able to independently set the base url, e.g. "apiv1" or "apiv2").