TODO(chalin): use $site-color-codeblock-bg

[woinbo]

we need to refactor these TODO's if someone interested does comment on this issue.

Find pages with TODO's, and refactor them by changing code or add new code to that file.

Here's a list of the 11 pages we should look at and eventually update (there might be more that don't show up due to improper formatting):

• Style Related

• TODO(chalin): use $site-color-codeblock-bg? link to file

• TODO(chalin): 1.5rem; link to file

• TODO: drop once heading class styles (like .h4) are fixed. link to file

• TODO: use / override BS defaults named $hX-font-size. link to file

• Dart analyze

• TODO @johnpryan: After dart CLI ships in stable, use dart analyze for all channels. link to file

• TODO(chalin): as of 2019/11/17, we don't need to select individual browser test files. Run browser tests over all files, since VM-only tests have been annotated as such.
  link to file

• Regexp

• TODO: maybe style special characters inside a regexp as punctuation. link to file

• Version related:

• TODO: identify versions (on line number 767)

• TODO: identify versions (on line number 781) link to file

• TODO: Next time we update this page, remove the toc line above. link to file

• Fix build instructions

• TODO (Instructions for compiling FFI example are broken #2219): Fix build instructions.link to file

• TODO: Give an example of how to deploy with Firebase, which originally was shown on link to file

• TODO: Improve the formatting of the following diff link to file

• TODO: (Improve generic extension docs #2171) link to file

• TODO: update that screenshot link to file

@kwalrath will assign the task's

[kwalrath]

Actually... What I meant was to file one issue per group of TODOs. So one issue for the style TODOs, one for the dart analyze TODOs, etc. Then create one or more PRs to point from each TODO to the relevant issue.

[woinbo]

Sorry, @kwalrath I took it wrong but I have fixed the mistake with these relevant issues #2859 #2860 #2861 #2862 #2863. I have one question what about the issues which don't lay in any category. Should I create one single issue for those?

[kwalrath]

Sorry, @kwalrath I took it wrong but I have fixed the mistake with these relevant issues #2859 #2860 #2861 #2862 #2863.

Thank you!

I have one question what about the issues which don't lay in any category. Should I create one single issue for those?

One issue per category-less TODO, please. Thanks again!