Deprecate ez_http_tag_location

[adriendupuis]

Question	Answer
JIRA issue	N/A
Type	Improvement/Misc
Target version	master
BC breaks	no
Doc needed	https://github.com/ezsystems/developer-documentation/pull/1297

Mark ez_http_tag_location as deprecated and ez_http_cache_tag_location as its alternative. If 2.5 BC is “to be cleaned up”, one should be informed to not using this and replace it.

TODO:

• [x] Implement feature / fix a bug.
• [ ] Implement tests + specs and passing ($ composer test)
• [x] Fix new code according to Coding Standards ($ composer fix-cs).
• [x] Ask for Code Review.

[vidarl]

@lserwatka So, this will be deprecated in 4.0 then (and possibly removed in 5.0) ?

[lserwatka]

This is already deprecated, we need to add a note in 3.3 and remove it in 4.0 as discussed offline.

[adamwojs]

@adriendupuis CI is reporting that code style needs to be fixed here. Could you please run composer fix-cs command, and then commit and push it's result? Thank you in advance,

[dabrt]

Dear gentlemen, when exactly were the two functions deprecated? I mean ez_http_tag_relation_ids() and ez_http_tag_relation_location_ids() Was it starting from 3.0 or 3.3?

[vidarl]

Communication wise, these were deprecated in 3.3.0 Technically, they will be deprecated in 3.3.2 ( if this PR gets merged by then )

[vidarl]

@adamwojs : ready for merge, right?

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication