Aaron Patterson 98c7fe8769 unwrap the constraints object on initialization, eliminate loops ... Unwrap Constraints objects. I don't actually think it's possible to pass a Constraints object to this constructor, but there were multiple places that kept testing children of this object. I *think* they were just being defensive, but I have no idea.		2014-05-24 17:52:22 -07:00
..
gtg	push move_string in to move	2014-04-01 15:58:42 -07:00
nfa	Replace map.flatten with flat_map in actionpack	2014-03-03 19:23:12 -08:00
nodes	update AD::Journey to follow Rails coding conventions	2012-12-20 15:42:39 -05:00
path	push the formatter up to the Route object	2014-05-21 14:27:30 -07:00
router	Make URL escaping more consistent	2014-04-20 10:11:38 +01:00
visualizer	Fix router visualizer CSS and JS resources	2014-05-23 20:38:34 -03:00
backwards.rb	:nodoc: Journey because is not part of the public API [ci skip]	2012-12-19 19:24:25 -05:00
formatter.rb	Remove AD::Journey::Formatter#verify_required_parts!	2014-05-23 18:00:50 +03:00
parser.rb	make the AST go from left to right, rather than right to left	2014-05-19 17:46:27 -07:00
parser.y	make the AST go from left to right, rather than right to left	2014-05-19 17:46:27 -07:00
parser_extras.rb	update AD::Journey to follow Rails coding conventions	2012-12-20 15:42:39 -05:00
route.rb	unwrap the constraints object on initialization, eliminate loops	2014-05-24 17:52:22 -07:00
router.rb	there is no formatter on the router object, so rm	2014-05-23 10:59:44 -07:00
routes.rb	Clear named routes when routes.rb is reloaded	2013-07-21 17:11:52 +01:00
scanner.rb	update AD::Journey to follow Rails coding conventions	2012-12-20 15:42:39 -05:00
visitors.rb	reuse path formatter from the non-optimized path.	2014-05-21 14:27:30 -07:00