|
14 | 14 |
|
15 | 15 | ### Hard
|
16 | 16 | * Finish killing Globals
|
17 |
| - * Guidelines: everything that isn't a CTOR should be closed inside `Env`, and everything that is a CTOR needs to be `new`ed inside the `Env` |
| 17 | + * Guidelines: |
| 18 | + * New objects can have constructors on `jasmine` |
| 19 | + * Top level functions can live on `jasmine` |
| 20 | + * Top level (i.e., any `jasmine` property) should only be referenced inside the `Env` constructor |
18 | 21 | * Spies
|
19 | 22 | * isA functions:
|
20 | 23 | * isArray_ - used in matchers and spies
|
|
26 | 29 | * argsToArray is used for Spies and matching
|
27 | 30 | * inherit is for how matchers are added/mixed in, reporters, and pretty printers
|
28 | 31 | * formatException is used only inside Env/spec
|
29 |
| - * htmlEscape is for messages in matchers - should this be HTML at all? Is that Reporter responsibility? |
30 |
| -* Suites need to be unit-tested |
31 |
| -* Remove Queue from Suite in favor of queuerunner refactoring |
32 |
| -* Remover Runner in favor of a top-level Suite |
33 |
| - * This means Env needs to `new` a `Suite` first thing |
34 |
| -* get feature parity back on HTMLReporter |
| 32 | + * htmlEscape is for messages in matchers - should this be HTML at all? Is that * Matchers improvements |
| 33 | + * move AddMatchers to Env & global (away from spec) |
| 34 | + * make matchers unit-testable |
| 35 | + * write doc on how to make a matcher |
35 | 36 |
|
36 | 37 | ### Easy
|
37 |
| -* Refactor `queuerunner` into a new object |
38 |
| -* xdescribe / xit make skipped specs instead of empty blocks |
39 | 38 |
|
40 | 39 | ## Other Topics
|
41 | 40 |
|
42 | 41 | * Build - can we, should we redo the build and release process AGAIN in order to make it less arcane
|
| 42 | + * Want to add JSHint to build |
| 43 | + * Use a standard JS/Node based concat system instead of custom Ruby? |
43 | 44 | * Docs
|
44 | 45 | * JsDoc is a pain to host and RubyMine is pretty good at navigating. I say we kill it officially
|
45 | 46 | * Docco has gone over well. Should we annotate all the sources and then have Pages be more complex, having tutorials and annotated source like Backbone? Are we small enough?
|
0 commit comments