-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add analyzer for resistor-color #13
Comments
@SleeplessByte I'd like to tackle this one. |
I'm digging through the code and found the
|
@zeckdude sure! Before you start writing code, please lay down the approach you'll take here. That gives us some time to merge #17 and #18.
These are the first 500 submission provided by Jeremy to me. I will ask Jeremy for edit: #24 done and done.
The statistics for the runner back then was this -- should be slightly different now: Statistics
#9 and specifically #9 (comment)
I don't quite understand what you're asking for. The batch runner outputs the analysis.json files into the fixture directories which you can use. Would you like a table of "fixture number" -> "output status" -> "output comments"? |
@zeckdude let me know if you have further comments. If not, I might go ahead and add a minimal solution for |
Raw output{
"invalid": 0,
"valid": 498,
"total": 498,
"unique": 309
} Parsing statisticsThis is the number of unique Abstract Syntax Trees after stripping commentary,
|
Since we have an initial analyzer, I'm closing this issue. |
This issue is for discussion and assignment for the
resistor-color
core exercise in thejavascript
track.🔗 implementation | mentor-notes | problem-specification
This exercise introduces the student to
Arrays
as well as showing that youcan export multiple bindings at once. Solutions using an
Object
will actively be discouraged as speed is not a good reasoning here.Optimal solution(s)
Approvable alternatives are:
SHOULD comment and disapprove
Cases we SHOULD comment on with this analyzer:
bind
to bindArray.prototype.indexOf
COULD comment (tips)
Cases we COULD comment on with this analyzer:
export
with a specifier (at the bottom of the file) can be doneexport const
inlineThe text was updated successfully, but these errors were encountered: