[CONTTAGS-37] Public vs. private API in content tags Created: 15/Sep/17  Updated: 10/Feb/21  Resolved: 30/Nov/17

Status: Closed
Project: Content Tags
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.1

Type: Story Priority: Neutral
Reporter: Antti Hietala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing CONTTAGS-108 Taggable is misspelt in config Open
is causing CONTTAGS-57 Freemarker can't differ two templatin... Closed
dependency
is depended upon by MGNLDEMO-249 TourList: find content tagged by all ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Kromeriz 114, Kromeriz 124
Story Points: 3

 Description   

Follow Magnolia API guidelines and annotate relevant parts of Content Tags as public API.

https://wiki.magnolia-cms.com/display/~mmuehlebach/Magnolia+APIs

(The API guideline is a draft. Improvement suggestions are welcome.)

CONTEDIT-150 is an example effort in the Content Editor module.


Generated at Mon Feb 12 00:24:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.