Caddy: Caddyfile support backtick strings

[caibirdme]

1. What would you like to have changed?

Caddyfile support multi line string

2. Why is this feature a useful, necessary, and/or important addition to this project?

without supporting of multi line string, it's difficult to develop some new plugins which need user to configure some complex string such as json.

3. What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?

directive here_might_be_a_json

# now
directive here_json_file_path

4. Please link to any relevant issues, pull requests, or other discussions.

[caibirdme]

If you approve this feature, I am willing to contribute

[mholt]

I believe the Caddyfile already supports multiline strings when enclosed in quotes.

[caibirdme]

@mholt I mean somthing like this:

`{
"name": "foo",
 "age": "bar",
}`

But now, we must do it like:

"
{\"name\":\"foo\",
\"age\":\"bar\"
}
"

[linquize]

Don't want to escape string

[mholt]

Ah, I see. So you want an alternate strings delimiter. Definitely possible.

[caibirdme]

Yes, it would be perfect if Caddyfile supports this

[mholt]

Feel free to submit a PR, I hope the implementation will not be too tricky!

Also consider if this could break anyone (I doubt it, but, worth considering.)

[caibirdme]

I'll try my best

[vaibhav2ghadge]

@mholt what happen about this feature..? if not implemented yet can you explain me what we wan to do.

[mholt]

I dunno, I never got a PR from @caibirdme -- I don't have the time to do it right now but you're welcome to submit a PR for review.

[vaibhav2ghadge]

@mholt can you explain what have to do. i mean which feature your expecting

[mholt]

As described above, I think multi-line strings delimited by ` is a good idea:

`{
"name": "foo",
 "age": "bar",
}`

[vaibhav2ghadge]

@mholt im not able to understand for which scenario this will be usefull i mean when this type of object will come from whom (how to generate this scenario)

[mholt]

Implemented in #3242, will go out by Caddy 2.1.