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
I would like to suggest some changes to the schema, so that the design of the new adaptive cards resemble more closely the known and used to webhooks messages.
Can we get the following added to the msteams schema so that the posted cards use more of the available screen estate before text-wrapping occurs?
this example would add a 2pixel height red line ontop of the adaptive card (for failures and errors on kustomizations.
and another one with a 2px height green line would be nice for successful reconciliations aswell :)
example red line card:
these changes should bring the adaptive cards into a more usable state, comparison of the current situation and diffrence here:
The text was updated successfully, but these errors were encountered:
psych0d0g
changed the title
increase Teams adaptive card notification width
Optimize Teams adaptive card style to be similar in readability and features to former webhooks
Oct 15, 2024
I would like to suggest some changes to the schema, so that the design of the new adaptive cards resemble more closely the known and used to webhooks messages.
see for reference:
https://learn.microsoft.com/en-us/answers/questions/932563/can-i-adjust-the-max-width-of-bot-chat-card
https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-format?tabs=adaptive-md%2Cdesktop%2Cconnector-html#sample-adaptive-card-with-full-width
this example would add a 2pixel height red line ontop of the adaptive card (for failures and errors on kustomizations.
and another one with a 2px height green line would be nice for successful reconciliations aswell :)
example red line card:
these changes should bring the adaptive cards into a more usable state, comparison of the current situation and diffrence here:
The text was updated successfully, but these errors were encountered: