Update API spec files to describe the correct class
What does this MR do?
Update API spec files to describe the correct class by changing API::API
to the corresponding class, for example API::AwardEmoji
.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Use Ruby conventions correctly.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Merge request reports
Activity
Please register or sign in to reply