Flag ActiveSupport::JSON in Gitlab::Json Cop
What does this MR do?
We have a Cop in place, Cop::Gitlab::Json
, which makes sure we prefer our own Gitlab::Json
wrapper over the json
gem.
However, it did not include a check that tests for ActiveSupport::JSON
, which we should also avoid for the same reasons.
This change makes sure the cop catches calls to ActiveSupport::JSON
as well and fixes existing cases.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Matthias Käppler