admin/jasmine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove jasmine.util.extend

Browse Source
This commit is contained in:
Davis W. Frank
2012-12-08 11:48:11 -08:00
parent 4ad43267ab
commit 668dd784ef
8 changed files with 32 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
GOALS_2.0.md
View File

@@ -14,9 +14,13 @@
### Hard
* Finish killing Globals
* Guidlines: 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`
* 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`
* Spies
* jasmine.util should be util closure inside of env or something
* argsToArray is used for Spies and matching
* inherit is for how matchers are added/mixed in, reporters, and pretty printers
* formatException is used only inside Env/spec
* htmlEscape is for messages in matchers - should this be HTML at all? Is that Reporter responsibility?
* Suites need to be unit-tested
* Remove Queue from Suite in favor of queuerunner refactoring
* Remover Runner in favor of a top-level Suite
@@ -24,5 +28,12 @@
* get feature parity back on HTMLReporter
### Easy
* Refactor `queuerunner` into a new object
* xdescribe / xit make skipped specs instead of empty blocks
* Refactor `queuerunner` into a new object
* xdescribe / xit make skipped specs instead of empty blocks
## Other Topics
* Build - can we, should we redo the build and release process AGAIN in order to make it less arcane
* Docs
* JsDoc is a pain to host and RubyMine is pretty good at navigating. I say we kill it officially
* 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?