Luis Lavena fe1ebb7d76 Correctly build key from detected parameters ... Given a key `/:foo/:bar`, the find mechanism was incorrectly picking the separator character as part of the key name (`foo/`). This caused incorrect match between expected name (`foo`) and the one obtained. When the key name was extracted from the named parameter, the size of the returned key was not compensated, given that we move +1 positions to avoid having ':' as part of the key. This is now corrected by reducing the key size one shorter to compensate. Fixes Issue #2		2016-02-29 11:40:18 -03:00
..
node_spec.cr	Extraction: initial import	2016-01-24 19:19:42 -03:00
result_spec.cr	spec: ensure Node usage is tracked	2016-01-24 19:21:19 -03:00
tree_spec.cr	Correctly build key from detected parameters	2016-02-29 11:40:18 -03:00