Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yellow border on Adaptive cards tab #2020

Closed
RabebOthmani opened this issue Aug 10, 2022 · 1 comment · Fixed by #2062
Closed

Yellow border on Adaptive cards tab #2020

RabebOthmani opened this issue Aug 10, 2022 · 1 comment · Fixed by #2062
Assignees
Labels
type:user-experience An issue related to user experience mainly ui/ux
Milestone

Comments

@RabebOthmani
Copy link

There is a little yellow rectangle that looks like a border?
IT's just next the copy button and can be confusing to users as it might look like a button
border

@RabebOthmani RabebOthmani added the type:user-experience An issue related to user experience mainly ui/ux label Aug 10, 2022
@ghost ghost added the ToTriage label Aug 10, 2022
@gavinbarron
Copy link
Member

This one is from the Monaco editor that is used to show the JSON here. It's not finding a schema for the JSON supplied and marking a warning, see the squiggly under the opening brace, along with a corresponding mark in the gutter.
image

I did some investigation and found that we can turn on the ability to load schema, but then I got a fetch failure.
Might be simplest to disable validation or set the schemaRequest issue to off from the default of warning.

Codesandbox exploring validation options: https://codesandbox.io/s/simple-usage-forked-plqtsf?file=/src/App.js

@ElinorW ElinorW self-assigned this Aug 29, 2022
@ghost ghost removed the ToTriage label Aug 29, 2022
@ElinorW ElinorW added this to the Aug-2022 milestone Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:user-experience An issue related to user experience mainly ui/ux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants