_meta: missing fieldOrder from query results

[yyyyaaa]

Reproduce:

• run new graphql services locally, or use production url, I'm gonna use local services
  http://dbe-admin.localhost:5555/graphiql

• fieldOrder should appear available for selection in _meta.tables.fields

If possible, walk me through it and I can add it

[yyyyaaa]

cc @pyramation

[pyramation]

Currently the plugin doesn't know anything about collections_public and will work on any database. fieldOrder is actually one of our fields.

The method for which _meta works, we technically don't have access to fieldOrder. We will have to see if we can get the native sql field order from the introspection query.

As a 2nd phase, we can consider making a v2 of _meta that incorporates our collections_public.

I will change the name of this issue and we can keep track of other fields we'd like to add to the _meta api

[pyramation]

@yyyyaaa please list anything else you can think of that may be helpful, that way we can plan best how to improve the meta api

fields to add

• label
• description
• field order

[yyyyaaa]

ah I see, I was mistaken, fieldOrder is a user-defined thing in their schema, if they don't define it, then it's not avail

[pyramation]

We could add label, description and fieldOrder as smart tags? so it would be in the exported schema that doesn't require collections_public but optionally would be there

[pyramation]

for now though, yea they don't exist yet