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

Style the instructional placeholder/comments #1156

Closed
galeyang opened this issue Jul 16, 2019 · 2 comments
Closed

Style the instructional placeholder/comments #1156

galeyang opened this issue Jul 16, 2019 · 2 comments
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 type-ux A user experience or user interface related issue
Milestone

Comments

@galeyang
Copy link

This is an indicator that guides users where to enter code in exercises.
// STEP 1: Put constructor here.
// TODO: Put constructor here.

Goal: allow users quickly identify where code should go

Currently we used comments for this purpose
image

It would be good to further style this placeholder
image

image

@galeyang galeyang added type-ux A user experience or user interface related issue P3 A lower priority bug or feature request from-study Issues are filed from a research study labels Jul 16, 2019
@RedBrogdon RedBrogdon added this to the Backlog milestone Jul 24, 2019
@InMatrix
Copy link

InMatrix commented Aug 6, 2019

Status of this issue is also tracked in https://github.com/orgs/flutter/projects/3.

@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
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 type-ux A user experience or user interface related issue
Projects
None yet
Development

No branches or pull requests

4 participants