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
Right now, the approach to show datacards for a konnector is
Check permissions and see if there is a data card for it
Each doctype can be mapped to a doctype in harvest = harvest knows that for io.cozy.timeseries.geojson,
it should be display a GeoDataCard.
Questions
What happens when we'll have multiple permissions that have a data card (files and bills) ?
Should the developer of the konnector be in control of what data cards are shown for its connector ?
Solutions
Choose only the first permission that has a viewer
Have a ranking on viewers = if the konnector fetches bills and files, we only show bills (bills > files in our hypothetical ranking)
Show all viewers in a tab like interface
Manifest of the konnector could express which datacard are to be shown
Even if the manifest of the konnector could express which data card is to be shown, I still think that we should have a default behavior that makes sense without the developer of the konnector knowing about data cards (so that we do not have to go through all the manifests and add this behavior ourselves).
The text was updated successfully, but these errors were encountered:
State right now
Right now, the approach to show datacards for a konnector is
Each doctype can be mapped to a doctype in harvest = harvest knows that for io.cozy.timeseries.geojson,
it should be display a GeoDataCard.
Questions
Solutions
Even if the manifest of the konnector could express which data card is to be shown, I still think that we should have a default behavior that makes sense without the developer of the konnector knowing about data cards (so that we do not have to go through all the manifests and add this behavior ourselves).
The text was updated successfully, but these errors were encountered: