Documentation for personal snippets lists wrong parameter (code instead of content)

There is confusion over whether code or content is the right parameter for snippets. Internally, the database stores content. However:

1. Project snippets use code: https://docs.gitlab.com/ee/api/project_snippets.html#create-new-snippet. This gets remapped here to content: https://gitlab.com/gitlab-org/gitlab-ce/blob/de385eee8507a35f1c01ca784ba9aab9bc38e11d/lib/api/project_snippets.rb#L63
2. Personal snippets use content: https://docs.gitlab.com/ee/api/snippets.html#create-new-snippet

@NikolayS @eread I think the documentation in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28571 is incorrect. I think you meant to use the first version, but updated the documentation in the second.

I think we should:

1. Revert back to using content -> code in the second case
2. Consider standardizing everything around content.

added devopscreate documentation typebug labels

added regression:12.0 label

changed the description

mentioned in merge request !32295 (merged)

mentioned in commit 6c61ed7d

mentioned in commit 562c354d

mentioned in merge request !32296 (merged)

mentioned in commit cbff48e6

mentioned in commit 88e97ef6

@stanhu I'm sorry about that. I didn't notice that data structures for projects snippets and personal snippets differ in API responses. I was fooled by the fact that snippets table has project_id and contents while API for project snippets requires code. (So, in the database schema, there is no difference, right?)

Indeed, it would be good to standardize it to have content everywhere.

Maybe it's worth emphasizing the difference between personal and project snippets in API description by:

• using the word personal next to snippet in all titles of https://docs.gitlab.com/ee/api/snippets.html#create-new-snippet
• changing Create new snippet to Create new project snippet in https://docs.gitlab.com/ee/api/project_snippets.html#create-new-snippet ?

@NikolayS, would you be happy to raise that MR, or would you like me to?

In the docs navigation, we could update to be more specific too:

@NikolayS Yeah, good suggestions.

I just standardized code and content in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/32296.

added regression label

mentioned in commit fc52421b

closed via merge request !32296 (merged)

mentioned in commit 955e23d9

mentioned in commit 98f2ab29

mentioned in commit 9fb5230f