Ian H comments

Results 18 comments of


                                            Ian H

Locals sent to render() from Sinatra should persist through to templates

They are not. If you pass current_user as a local when rendering a top-level template, that current_user object is not available when you're rendering via template() inside the top-level one.

Locals sent to render() from Sinatra should persist through to templates

Sounds right to me.

attribute option to indicate if a blank values' key should be included in the output

Is there a global setting as well?

attribute option to indicate if a blank values' key should be included in the output

Would prefer something a little more semantic, like :include_blank_attributes

attribute option to indicate if a blank values' key should be included in the output

Sorry, last arg was from an object/collection standpoint.

attribute option to indicate if a blank values' key should be included in the output

So maybe you're right, as a start just add the include_blank => true and we can add options higher up the stack if a general control of objects is necessary.

Not listening on 4000

Ah. I think that was the confusion. I really like how nextjs and other platforms have a `npm start` as a production server running against a build and `npm run...

filterSchema typeFilter unexpected behavior

Interestingly enough, if you run the filtered schema through `pruneSchema` twice, it corrects the dangling subscription type.

ord returns different results in JS than PHP

@kvz any thoughts on what I might be doing wrong? Would appreciate any help or insight you might have.

conflict with serverless-webpack

@zhenyulin did you end up solving this?