Trevor Parscal b4de3ead08 Throw ve.Error instead of string literals ... Throwing strings is bad because it doesn't include a lot of important information that an error object does, such as a stack trace or where the error was actually thrown from. ve.Error inherits directly from Error. In the future we may create more specific subclasses and/or do custom stuff. Some interesting reading on the subject: * http://www.devthought.com/2011/12/22/a-string-is-not-an-error/ Change-Id: Ib7c568a1dcb98abac44c6c146e84dde5315b2826		2012-08-08 06:19:00 +02:00
..
inspectors	Cleanup - all jshint conditions are now met	2012-08-03 18:56:04 -07:00
styles	Kranitor #3: jQuerlyfornication ft. The Cascaders	2012-07-28 13:05:57 -07:00
tools	Throw ve.Error instead of string literals	2012-08-08 06:19:00 +02:00
ve.ui.Context.js	Throw ve.Error instead of string literals	2012-08-08 06:19:00 +02:00
ve.ui.Inspector.js	Kranitor #1: On-boarding	2012-07-27 14:40:00 -07:00
ve.ui.js	Added ve.init.platform with MediaWiki and stand-alone implementations	2012-07-27 13:39:19 -07:00
ve.ui.Menu.js	Throw ve.Error instead of string literals	2012-08-08 06:19:00 +02:00
ve.ui.Tool.js	Throw ve.Error instead of string literals	2012-08-08 06:19:00 +02:00
ve.ui.Toolbar.js	Puttin' em white-spacers where they aught'a be	2012-08-06 18:52:19 -07:00