[5.5] Add a new line after the @json blade directive

[chrisbjr]

This pull request adds a new line after the JSON encoding of the @json blade directive.

We've experienced a bug when using the @json blade directive in the following scenario:

<script>
  var foo = @json($foo)
  var bar = 2
</script>

The above output will return something like this:

<script>
  var foo = {"id": 1}    var bar = 2
</script>

Obviously, we get a syntax error with that output. Adding a new line at the end of @json fixes this problem and will return the following output:

<script>
  var foo = {"id": 1}    
  var bar = 2
</script>

[sisve]

Is this really specific to the @json directive? What if I have actual inline json? Wouldn't it be more reasonable to change so that the regex (or whatever does it) doesn't match/consume the newlines after the ending paranthes?

[themsaid]

What if I'm passing it inside a method that has other params? I won't want a new line in this case.

[taylorotwell]

We may want to update the docs to show putting a semi-colon after the json directive

[chrisbjr]

Good points. Totally overlooked those scenarios. This won't happen with a semicolon but we've just recently switched to following StandardJS so no semicolons for us supposedly. I wonder why the new line is getting removed after declaring the blade directive in this scenario though.

var foo = @json($foo)
var bar = 2

currently doing this to go around no semicolons:

var foo = @json($foo)

var bar = 2

[franzliedke]

Ah, the good old newline eating.

I've sent a PR to the docs with a note that explains (and warns about) this behavior. Oh, and it adds the semicolon.