Issue Summary

When running under Node 14, the error message printed out when a second instance of Ghost is trying to bind to a port isn't the custom one we have, but the generic one.

To Reproduce

1. Use Node 14
2. Run an instance of Ghost
3. Attempt to run another instance of Ghost on the same port
4. 💥

We have a check like error.errno === 'EADDRINUSE', which evals to `fa

I used the Directus app to add a O2M field to a collection with a lot of items, and choose to add the corresponding M2O field to the related table.

When visualizing the collection hosting the O2M field, that field indicates "100 items" and it's only possible to scroll through these 100 items, even though there are way more.

Would it be possible to skip that limit, to change its value, or jus

• Are you running a release or master: master
• Issue is about a fresh instance (no data in db) or restart: fresh

This seems a known/unfinished issue based on the commented 'Name' field in the code noted below, but I was hoping it could be addressed as it would greatly ease the discovery of the graphql endpoints generated by the db tables as they would become available in GraphiQL in #13

``

Class AbstractReflectionPropertyFieldResolver automatically exposes all the properties from a provided class, to easily create its FieldResolver.

Since in PHP 7.4 class properties can be typed, we can extract the types to return in function getSchemaFieldType.

The page needs to be doublechecked and reviewed.

https://github.com/arduosoft/RawCMS/blob/features/logcollecting/docs/LogCollecting.md