Docs Invalid JSON Examples for System Hooks

Summary

Note that this is only a 'bug' in the documentation, not the application misbehaving.

Several JSON examples in the document describing the system hooks contain a trailing comma after the last member pair. This is invalid according to the JSON specification. Any reasonably strict parser will refuse to parse the offending examples.

The incorrect examples are:

• Project created
• Project destroyed
• Project renamed
• Project transferred
• Project updated
• New Team Member
• Team Member Removed

Later examples in the document do not contain the trailing comma.

Steps to reproduce

Copy one of the examples from document describing the system hooks that contains a trailing comma into a JSON validator like jsonlint.com and observe the error message.

What is the current bug behavior?

The JSON is invalid due to the trailing comma.

What is the expected correct behavior?

The JSON is valid and does not contain a trailing comma.

Relevant logs and/or screenshots

Output of checks

This bug happens on gitlab.com.