You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing things like creating custom providers it would be nice to have typescript definitions for all the data that is returned through the getData function. In particular the configuration data like meta, relationships etc. With that it would be easier for the developers to know what is required or can be used for different scenarios. Taking away some of the problems away when you can spend only some stuff back but if you don't send enough information back about the dataset you get odd errors that are not easy to debug. Mostly I think the types for the configuration information in Featureserver being the most prominent. I have some examples that I have thrown in my local project to help us along.
exportinterfaceRelationship{id: number,// The unique relationship id.name: string,// The name of the relationshiprelatedTableId: number,// Id of the layer/table related records are foundcardinality: string,// esriRelCardinalityOneToMany | esriRelCardinalityManyToManyrole: string,// esriRelRoleOrigin | esriRelRoleDestinationkeyField: string,// key field name in the related Tablecomposite: boolean// likely to false}exportinterfaceMetadata{id: number,name: stringdescription: stringextent?: number[][]displayField?: stringgeometryType?: stringidField?: stringmaxRecordCount: numberlimitExceeded?: booleanfields: Field[]}
The text was updated successfully, but these errors were encountered:
When doing things like creating custom providers it would be nice to have typescript definitions for all the data that is returned through the getData function. In particular the configuration data like meta, relationships etc. With that it would be easier for the developers to know what is required or can be used for different scenarios. Taking away some of the problems away when you can spend only some stuff back but if you don't send enough information back about the dataset you get odd errors that are not easy to debug. Mostly I think the types for the configuration information in Featureserver being the most prominent. I have some examples that I have thrown in my local project to help us along.
The text was updated successfully, but these errors were encountered: