[MAGNOLIA-2927] Introduce generics in various classes Created: 03/Nov/09  Updated: 23/Jan/13  Resolved: 01/Apr/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.1.1
Fix Version/s: 4.3

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: File core-generics.patch    
Issue Links:
dependency
depends upon MAGNOLIA-2886 Introduce generics in the content api Closed
is depended upon by MAGNOLIA-3078 Generics in User API classes Closed
relation
is related to MAGNOLIA-3029 Use generics for ObservedManager Closed
is related to MAGNOLIA-2725 c2b: use generics to find the type to... Closed
is related to MAGNOLIA-2926 Refactor/move/repackage the info.magn... Closed
is related to MGNLCMNT-23 Generics for commenting module Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-3028 Introduce generics in mail module Sub-task Closed Magnolia International  
MAGNOLIA-3081 use generics in the rendering model (... Sub-task Closed Philipp Bärfuss  
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   

such as for example

  • QueryUtil or
  • FactoryUtil

See comments for change log / status !



 Comments   
Comment by Jan Haderka [ 01/Dec/09 ]

Patch with generics for the util classes and C2B. Apply once the trunk moves to 4.3 (or higher major version)

Comment by Magnolia International [ 05/Jan/10 ]

There's a patch to info.magnolia.cms.util.DelayedExecutor that has absolutely nothing to do with this.
FactoryUtil and other classes also have changes that are style/taste related (removal of end-of-block elses) as well as indentation. This hinders readability/safety of patch applying. To avoid in general. (indentation can't hurt, but the else thing could; if there's a good reason for such changes (there aren't), it should be consistent and a separate patch, ideally)

Additionally, since this covers such a broad range of classes, when committing, it'd probably be a good idea to split (c2b, factory/class utils, other utils, ...)

Generated at Mon Feb 12 03:41:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.