Dan Cunningham
Dan Cunningham
Great, thanks for the quick feedback. I just updated the binding PR to support this and was able to test end to end with a IOS client.
> What about allowing an Image or Video Item name as value for media-attachment-url? I was also thinking to allow relative paths like `/static/html/....` and we would try hitting the...
@florian-h05 correct, binding and cloud code should not care. I think we can detect url patterns , maybe even item://imageItem or something like that for advanced use of pulling of...
btw, cloud code is deployed, so the binding should work in production
So I started to actually use this feature on my home system, very very cool 
@ghys i'll definitely read up on browser notifications, its an area i know very little about, but it does sound like an awesome feature, especially if there might be a...
@jimtng those sound like good ideas. The way IOS works, for `http(s):` i think we would need to bring the app to the foreground first (like we do with `ui:`)...
when using image items for the `media-attachment-url` , how about using `item:myItemName` ? This can still be parsed as a valid URI in both Swift and Kotlin for easy parsing...
So the IOS app now supports using the `item:itemName` format for media attachments, i'm waiting on testflight to approve our initial build so we can start getting users on it...
I updated the actions description to include http/https links in actions , this has also been added to the IOS client.