Open
Conversation
Member
|
Hi Anna, I don't think this is valid syntax to access into an array. |
Contributor
Author
Hey @jwoo-msft! That sample is confusing - sorry! That is the previous behavior that the PR fixes. If you try to use the If you want to see the new behavior, I can kick off another ci build for this branch. |
Member
|
Hi @anna-dingler , [$root.employees[0]] works, but 'employee[0]' is just a string in AEL expression. |
jwoo-msft
reviewed
Jun 26, 2024
| let modifiedName = qualifiedName; | ||
|
|
||
| // If we include `[0]` in the qualified name while determining if we should use indexer syntax, | ||
| // We could incorrectly wrap the name in [] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Fixes #8013
Description
When generating the templating variable from the
Bind...button in the designer, we have an edge case for data variables that contain special characters. In this scenario, we typically want to use index syntax and wrap the var in braces.However, this does not work for arrays. For arrays, we index into the first element by appending
[0]to the name. This forces the index syntax incorrectly because the name now includes special characters.I updated the logic to remove
[0]from the end of array type names before checking for special characters.Sample Card
{ "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "wrap": true, // Add text property manually in the designer and Bind to `name` } ], "data": { "employees": [ { "name": "Gabriela Leticia" }, { "name": "Natalia Tercera" }, { "name": "Waleska Cristobal" } ] } }How Verified
Verified on the CI site.