-
Notifications
You must be signed in to change notification settings - Fork 0
/
new-linter-service.txt
41 lines (36 loc) · 1.12 KB
/
new-linter-service.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Once ragger is working think about the customizations like James does, eg
- detecting printf's in the source
- detecting lack of coverage
- a lot of ambers in a row
- that was a big change!
This could be bundled into the ragger. Viz the ragger is
generalized and is passed a hash containing lots of data
not just stdout,stderr,status.
However, I think it might be simpler as a SEPARATE service.
A linter/adviser/helper service.
It would expose a function, maybe a lambda in the browser.
Initially in Ruby, later in any language? eg Python
It would be passed much more information than the ragger,
probably in a hash, eg, stdin ==> hash['stdin']
- stdout,stderr,status
- timed_out (true/false)
- traffic-light-colour :red,:amber,:green,:faulty
- previous traffic-light sequence
- duration (secs.msecs)
- all new_files
- all old_files
- created filenames
- changed filenames
- deleted filenames
- diff from previous files
Possible names like linter...
advisor
helper - simple. Could output to a new std file, eg stdhlp
mentor
marker
evaluator
grader
assessor
appraiser
feedbacker
signaller