Nick Pelone

Nano-update on my workaround: It also appears that the type tag parser is interpreting my type as a String? Or maybe I'm just reading this wrong?   (notice in...

Hey, thanks for the update! Much appreciated :smile:

Sweet! After updating, things no longer crash with an `@prop {?Error}` annotation. As you said, the typcheck on the binding still shows as incorrect, but I can patiently await that...

With Mustermann/Sinatra 2.0 I believe the preferred form is to use a group and then make it optional at the end, eg: `/user(/:id)?` where the above would match `/user`, `/user/1`...

You're missing the `?` at the end, which tells the pattern matcher that the group is optional: #### example.rb ```ruby require 'sinatra' get '/user(/:id)?' do [200, params.to_s] end ``` -...

Oh ok, thanks for the clarification - and actually I'm fine with the current behavior, I was just curious as to the exact mechanics by which it "added stuff into...

I hate to necrobump this, but is there any hope of getting this fixed or should I migrate code to use `# @!parse`? I've had to hold off on upgrades...

I unfortunately kinda want to agree with @jstclair ....hello? Everyone busy on Polymer 3 or something?

Personal +1. I was not able to launch TF2/x64 native on Linux until I passed the `-windowed` option to stop it from crashing / nuking my X server. (I hope...

I personally noted today this seems to be resolved - I don't know if it was a change in my system, or some kind of quiet update, or what. I'll...