allowedCapabilityTypes should support 'object'

Question

allowedCapabilityTypes should support 'object'

irritanterik opened this issue 9 years ago · 6 comments

Object typed capabilities are needed for capabilities like long latitude locations or other multi-dimensional datapoints.
This is an undocumented breaking change as of version 0.9.1.

Answer 1 · 2016-08-01T09:16:38.000Z

That would be really hard to validate. Wouldn't string suffice in this case? e.g. 50.654,7.3484

Answer 2 · 2016-08-01T09:21:38.000Z

I'll try to get it working with a string and JSON.stringify(), but don't like the coding and decoding necessary in backend and frontend when implementing custom mobile cards.

Answer 3 · 2016-08-01T09:26:10.000Z

Hm, as custom components aren't supported for now, how would you then display it in a mobile card?

Answer 4 · 2016-08-01T09:37:08.000Z

Ah. Thought it was supported as of v 0.9.1. My mistake. Eventually want to do something like:

Answer 5 · 2016-08-01T09:49:45.000Z

Alright. When creating support for custom mobile cards I'll keep that in mind!

Answer 6 · 2016-08-01T09:50:29.000Z

Thanks. Close this issue for now.