[BLOSSOM-26] RepositoryUtils.hasLocalNodeData would be convinent to have Created: 06/Dec/10  Updated: 07/Nov/14  Resolved: 07/Dec/10

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Trivial
Reporter: Kimmo Björnsson Assignee: Tobias Mattsson
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:

 Description   

RepositoryUtils.hasNodeData is nice to have but if I want to check for a local node data quick I can do this now:
RepositoryUtils.hasNodeData(RepositoryUtils.getLocalContentNode(), "myId"))

It would be nice with a:
RepositoryUtils.hasLocalNodeData("myId")

Similar to RepositoryUtils.getLocalNodeData vs. RepositoryUtils.getNodeData



 Comments   
Comment by Tobias Mattsson [ 07/Dec/10 ]

RepositoryUtils is intended for (although not limited to) internal use by the module. You can easily write a utilities class of your own with the methods that you find convenient. Also, in the upcoming version the additions made in BLOSSOM-23 will allow you to have the Content object of the template/paragraph passed as an argument to your annotated controllers.

Generated at Sun Feb 11 23:29:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.