Support for pre-fill forms on the ask page

[fenbox]

Is your feature request related to a problem? Please describe

As mentioned in #252, we need some pre-fill support when ask question.

Describe the solution you'd like

When visiting a link with a pre-fill parameter, the form content will be automatically filled.

Link: /questions/ask?prefill={{ markdown_parameter }}

{{ markdown_parameter }}:

---
title: hello world
tags: feature-request, template
---

Some body text...

Result:

[hgaol]

Hi @fenbox , I'd like to try this task, thx! BTW, do we need the functionality of adding, updating, getting and deleting of a question template?

[fenbox]

Hi @hgaol, the function of managing templates can be implemented by plugins in the future, which is not part of the core program.

[hgaol]

Hi @fenbox and @shuashuai , how about using json format for {{ markdown_parameter }} and keep the same structure with draft in local storage. e.g.

{
  "tags": [],
  "title": "title",
  "content": "Hello World",
  ...
}

Cause I found it's not easy to parse markdown to get the metadata like tags, title. Pls let me know if any suggestion.

[shuashuai]

Hi @fenbox and @shuashuai , how about using json format for {{ markdown_parameter }} and keep the same structure with draft in local storage. e.g.

{
  "tags": [],
  "title": "title",
  "content": "Hello World",
  ...
}

Cause I found it's not easy to parse markdown to get the metadata like tags, title. Pls let me know if any suggestion.

From a technical point of view, this is indeed the case. Using json is more intuitive and easier to parse.

[fenbox]

I prefer markdown because markdown format will be more convenient for operators in non-technical industries to maintain, and there are already typical system cases.

• There are two types of issue templates on GitHub: one is in markdown text format, and the other is in YAML configuration form.
• The case of dev.to is markdown.

Note

In the tag section, only existing tags can be input. If a tag in template does not exist, it will not be displayed and not able to be added.

[shuashuai]

I agree with the above point of view.

The case of dev.to is markdown.

I also prefer this solution

pr #1014 This solution simplifies the implementation of the technology, but it can be significantly more difficult for the user to use.

From a technical point of view, this is indeed the case. Using json is more intuitive and easier to parse.

I'm sorry, I wasn't thinking in terms of user usage.

[hgaol]

Good point, sure, I'll update #1014 to use markdown format.

[hgaol]

updated to support markdown format. It'll use title and tags metadata to pre-fill title and tags. But the content should be encoded (encodeURIComponent in js) before as a parameter to avoid special characters.