[FieldFactory] Handle *to many* references

[lutangar]

The FieldFactory does'nt support to many references.
ReferenceManyField should be used instead of a ReferenceField.

Apparently, there is no facts in a doc to disguinsh a property referencing many resources from a property referencing only one resource.

Still, the plural form of a property name could be detected, but that would still be a wild guess...

Another approach would be a higher order component which will choose between a ReferenceField and a ReferenceManyField once populated by data: the data would be an array or not.

But this feels dodgy as well, there must be a way to find the right field before data population.

What's your toughts on this?

[dunglas]

Doing this at runtime is the only reliable way. Both Hydra and Schema.org don't distinguish to-n or to-1 relationship (it can be both, it can only be detected at runtime), and the final s convention has been dropped from Schema.org for this exact reason.

So the HOC looks like the only way to go.

[Simperfit]

Closing as this got no feedback