microsoft / adaptivecards Goto Github PK

A new way for developers to exchange card content in a common and consistent way.

License: MIT License

CSS 2.95% HTML 0.16% TypeScript 15.38% JavaScript 5.31% C# 26.87% C++ 23.84% C 0.31% CMake 0.09% Java 12.57% Objective-C 2.19% Objective-C++ 9.09% Ruby 0.05% Batchfile 0.12% PowerShell 0.20% SWIG 0.57% ANTLR 0.03% Makefile 0.01% Swift 0.04% SCSS 0.20% Shell 0.02%

cards bot-framework adaptive-cards adaptivecards adaptive xaml wpf xamarin ios android

adaptivecards's Issues

Automatically deploy the Visualizer to a hosted site on build

HTML renderer enable strictNullChecks and noImplicitAny

Flesh out "House of Cards" concept

Allowing a single payload to house multiple Card variations. E.g., a developer could include an AdaptiveCard targeting Skype, an FbCard targetting FB Messenger, and a SpeechCard meant to being read on a headless device.

This should also cover the the Skype scenario where a Card has a Collapsed and FullScreen view, as seen here on Facebook Messenger:

Host App for UWP Renderer

User-friendly errors in the Visualizer with malformed JSON

Tooling to validate json payload against the schema

Add Sports Summary card

Similar to

Create Bot that generates Adaptive Card responses

Section "title" property

Example seen in FlightIntinerary.

               {
                                                "title": "Passengers",
                                                "separator": "bottom",
                                                "items": [
                                                                {
                                                                                "@type": "TextBlock",
                                                                                "text": "Sarah Hum"
                                                                },
                                                                {
                                                                                "@type": "TextBlock",
                                                                                "text": "Jeremy Goldberg"
                                                                },
                                                                {
                                                                                "@type": "TextBlock",
                                                                                "text": "Evan Litvak"
                                                                }
                                                ]
                                }

Semantics:

Always displayed at the same location within the section (probably at the top)
Always rendered using a very specific font (size, weight, color)
Possibly useful for accessibility or speech-devices

BotFramework translation to 3rd-party channels

Integrate WebChatControl with AdaptiveCard Renderer

TextBlock isSubtle property

Should we make subtle a textColor semantic value versus the isSubtle property. Is it useful to combine them?

{ textColor: "warning", "isSubtle": true }

Google Now scenario validation

Update Toast to simulate pulling app logo and remove from payload

CalendarReminder.json shouldn't have a ColumnGroup in it. The Visualizer should simulate pulling an app logo and display name and not be part of the payload itself

IntelliSense in Visualizer

Published Visualizer needs a way to browse Scenario payloads without local copies

Visualizer supports domain-specific payloads

A User can paste in a full Timeline or Bot payload and visualize the adaptive section

Multi-targeting a single payload to multiple containers

Prototype translation layer from Adaptive XML to Adaptive JSON

Rationalize BF suggestedActions with AdaptiveCard actions property

Per team meeting on 1/3

Add Receipt Card sample

Host App for Android Renderer

Renderer allows containers to support custom types

Scenario: Toast Notifications have a progress bar in their payloads

 "body": [
                    {
                        "type": "TextBlock",
                        "text": "Serious Pie",
                        "textWeight": "bolder",
                        "textSize": "medium"
                    },
                    **{
                        "type": "ProgressBar",
                        "Value": "50"
                    }**
                ]

The Renderer should provide some kind of callback to the container to handle generating UI for any unknown types

Card versioning and fallback

Problem

If a bot developer absolutely requires a v2 renderer, and fallback would not be appropriate, they can add this attribute and the renderer would output something like “Unfortunately this content couldn’t be displayed”

Schema

version is a required property on all payloads.
minVersion is an optional property that allows a developer to declare that their card must only be renderered on a supported version.

Example

{
    "$schema": "../../schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "99.0",
    "minVersion": "99.0",
    "fallbackText": "This card requires Adaptive Cards version 99.0, which probably doesn't exist",
    "body": [
        {
            "type": "TextBlock",
            "text": "THIS SHOULD NOT APPEAR! It should show the fallback text"
        }        
    ]
}

Renderer spec

A renderer MUST implement a particular version of the schema.
If a renderer encounters a minRequiredVersion property in the AdaptiveCard that is higher than the supported version, it MUST return the fallbackText instead.

Update schema documentation once draft is ready

AdaptiveForm proposal

Sections should not be mandatory for simple cards

Accessibility review

BotFramework C# SDK has API to generate payload

Live Tile using JSON

// TODO: Do we have MRT issues?
// TODO: What about high contrast?
// TODO: LTR and RTL
// TODO: Should we add TileGeneric?
// TODO: Narrator support

{
    "branding": "none",
    "TileSmall": {
        "branding": {},
        "visual": [
            
        ]
    },
    "TileMedium": {
        "branding": {},
        "visual": [

        ]
    },
     "TileWide": {
        "branding": {},
        "visual": [
            
        ]
    },
    "TileLarge": {
        "branding": {},
        "visual": [
            
        ]
    }
}

Remove requirement of root sections property

For simple cards they should be able to put TextBlock right inside the AdaptiveCard items. Or a ColumnGroup, or whatever they choose

Renderer generating bitmaps

Should this be built into the renderer or left up to the host app?

Handling of expanded/collapsed views in a single payload

Add Cortana Card experiment to Visualizer drop down

Sections become more semantic

Toast Notifications using JSON

// TODO: Handle actions with input
// TODO: What about inputs that don't have actions?
// TODO: Can we go semantic with title, description, etc

{
	"@type": "AdaptiveCard",
	"title": "Adaptive Card design session",
	"description1": "Conf Room 112/3377 (10)",
	"description2": "12:30 PM - 1:30 PM",
	"body": [
	    {
	        "@type": "TextBlock",
	        "text": "Snooze for"
	    },
	    {
	        "@type": "MultichoiceInput",
	        "size": "stretch",
	        "choices": [
	            { "display": "5 minutes" },
	            { "display": "15 minutes" },
	            { "display": "30 minutes" }
	        ]
	    },
	    {
	        "@type": "ActionGroup",
	        "items": [
	            {
	                "@type": "HttpPOST",
	                "name": "Snooze"
	            },
	            {
	                "@type": "HttpPOST",
	                "name": "I'll be late"
	            },
	            {
	                "@type": "HttpPOST",
	                "name": "Dismiss"
	            }
	        ]
	    }
	]
}