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.

Sign up for GitHub

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

Jump to bottom

In custom error message, provide specific fixes to an error upon user request #1245

Closed
galeyang opened this issue Sep 6, 2019 · 1 comment
Closed

In custom error message, provide specific fixes to an error upon user request #1245

galeyang opened this issue Sep 6, 2019 · 1 comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant from-study Issues are filed from a research study P3 A lower priority bug or feature request
Milestone
Backlog

Comments

@galeyang
Copy link

galeyang commented Sep 6, 2019 •
edited
Loading

Currently exercise authors can provide custom error messages mapping to tests. It's recommended to offer clear and targeted test results and hints (what might be wrong).

In the previous UX study, a few participants would like to see a suggestion on how to fix a specific error (or failed test). However, some other participants felt providing a specific fix is giving out the learning opportunity.

To better support both needs, we can consider providing specific fixes to an error upon user request.

Status of this issue is also tracked in https://github.com/orgs/flutter/projects/3.
@galeyang galeyang added P3 A lower priority bug or feature request from-study Issues are filed from a research study labels Sep 6, 2019
@RedBrogdon RedBrogdon added this to the Backlog milestone Sep 11, 2019
@parlough
Copy link
Member

As part of the new, simplified version of the DartPad frontend, the exercise functionality this was related to was removed.

If anyone would like to see similar functionality brought back, please check out #2702 or open a new issue. Thanks so much!

@parlough parlough closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2024
@parlough parlough added closed-stale Closed as the issue or PR is assumed stale. closed-obsolete Closed as the reported issue is no longer relevant and removed closed-stale Closed as the issue or PR is assumed stale. labels Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-obsolete Closed as the reported issue is no longer relevant from-study Issues are filed from a research study P3 A lower priority bug or feature request
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@RedBrogdon @galeyang @parlough