Leading slash on nested single routes breaks router

[darkofabijan]

Leading slash on nested single routes breaks router

[chrismccord]

I'd rather support just one if we can, but I could see end users interchanging with and without, so perhaps the extra effort to support both would save needless debugging? Leading slash does feel slightly more natural. Do you want to make it happen?

Per the example, this is where member/collection macros come in, but the smarter path join might be a good options in general since I could see people mixing/matching.

[darkofabijan]

Supporting just one sound cleaner to me. Maybe we can just raise compile time exception if path is missing leading slash? That way we would not have to handle both cases and end users would be saved from debugging. Maybe I could try it and see how it feels. Yea I could try to fix it :)

After working on scopes I am not that much afraid of all that nesting macros game any more. Your context stack based concept works really well.

[chrismccord]

Awesome. I think the raise makes sense. Convention over config means making the trivial choices for everyone, so I think this qualifies. Please go ahead.