Roman Shtylman

Results 350 comments of Roman Shtylman

Please add app.route('foo').use()

I think having a route.use() that strips the path could be interesting. It would allow you to built up trees of routes minimizing repeating the same route string. I support...

Please add app.route('foo').use()

`route.use(fn)` because the path is built in already

Please add app.route('foo').use()

Yea, actually I think you are right in that it should support `(path, fn)` if it supports anything at all.

Please add app.route('foo').use()

Right, the `.use` would be path after stripping away the route's path. Then it could strip away any additional path you pass as well.

Please add app.route('foo').use()

It seems that having this feature is useless then?

deprecate app.render (make private)

Any particular reason why? On Friday, November 21, 2014, Jeremiah Senkpiel [email protected] wrote: > @dougwilson https://github.com/dougwilson should we target this for 4.x > deprecation? > > Tbh I can't even...

Upgrading to node v4/v5 version

I would absolutely accept a PR :) On Friday, February 5, 2016, Guillaume Plique [email protected] wrote: > Hello @defunctzombie https://github.com/defunctzombie. I was just > wondering whether you considered upgrading the...

Could not resolve to a node with the global id of '******'

@mattcosta7 Any thoughts on what I should try here? Or any additional info I can provide for debugging? I've got several private repos (in the same organization as my project)...

Could not resolve to a node with the global id of '******'

@skw I've double checked - our secrets (created at the org level) use the "selected repositories" option and I also confirmed they are shared with the repositories where I am...

Could not resolve to a node with the global id of '******'

I've moved to a custom github bot app instead of the action because I wanted to apply these behaviors to my entire org and found the repo-by-repo approach too manual....