namusyaka

@304 First off, thanks so much for proposing the idea and working on that. Overall seems good to me. To be honest, I don't think Rubocop is always good because...

I know your contributions and other incoming PRs exist, but I have been ultra busy now. I'll try to review those by next month. Sorry for the inconvenience.

@adbatista Great, thanks for your kindness comment. To everyone: I'm thinking how we make v3.0.0 more great for a lot of rubyists. This is a new idea: - How about...

@epergo thanks for writing down, I like your ideas. Overall seems reasonable to me. @jkowens Any thoughts?

Creating...: @sinatra-bot

PR has been attached #1515

First of all, you should use `(/:bar)?` as an optional parameter instead of `:bar/?`. The captured name depends on the context. Therefore, I think the behavior is not a bug.

>The optional parameter is baz in the example, not bar. '/foo/:bar/?:baz?' (my apologies for the confusing names in the example). Both ways of defining an optional parameter seem to work...

I think this is not a bug, but I'd like to keep this issue for discussing the API-design. @lvonk Thanks for your report. cc @zzak

@genkami Could you provide an example for reproducing the error?