15 Commits

Author	SHA1	Message	Date
Akihiko Odaki	b13cc6f39a	Do not encode characters allowed in path when generating routes ... In RFC 3986, some characters not allowed in query, which encodeURIComponent is designed for, is allowed in path. A notable example is "@", which is commonly included in paths of social profile pages. Such characters should not be encoded. The new encoding function is conforming to the RFC.	2018-04-14 01:08:27 +09:00
Rich-Harris	25809ec409	enforce stable sort	2018-03-25 15:12:35 -04:00
Rich Harris	ef55fc5ddd	move built files to dist	2018-03-10 23:20:11 -05:00
Rich Harris	254e41b11e	use code-splitting etc	2018-03-10 22:26:53 -05:00
Rich Harris	8bb0999878	fix route sorting	2018-03-07 14:26:30 -05:00
Rich Harris	58c1eb9fa8	allow dynamic parameters inside route parts - fixes #139	2018-02-28 09:39:21 -05:00
Rich Harris	fc631c4866	make route handling more explicit	2018-01-21 15:41:13 -05:00
Rich Harris	dd8deb2d8a	wip 3	2018-01-21 14:41:11 -05:00
Rich Harris	7d721abb2a	wip 2	2018-01-21 11:15:32 -05:00
Rich Harris	39b1fa89ce	wip	2018-01-21 11:03:23 -05:00
mrkishi	8a8526d9ed	Identify js and html route clashes	2018-01-20 01:42:13 -02:00
Rich Harris	423e02aeae	handle nested routes - fixes #55	2017-12-31 13:25:52 -05:00
Rich Harris	f50d3c4262	error if routes clash - fixes #33	2017-12-20 20:46:28 -05:00
Rich Harris	c1b1b3ed63	add some tests - closes #10	2017-12-18 21:39:17 -05:00
Rich Harris	8da3ca16ab	Separate build step (closes #21)	2017-12-18 15:38:56 -05:00