No Code Attached Yet bug
avatar robbiejackson
robbiejackson
8 Jan 2023

There is a naming inconsistency in the method names in \libraries\src\Association\AssociationServiceTrait.php

The getter is called getAssociationsExtension() with an s at the end of Association

The setter is called setAssociationExtension() without an s at the end of Association

Not sure if you feel this warrants getting fixed or not!

avatar robbiejackson robbiejackson - open - 8 Jan 2023
avatar robbiejackson robbiejackson - change - 8 Jan 2023
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 8 Jan 2023
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 8 Jan 2023
avatar wojtekxtx
wojtekxtx - comment - 10 Jan 2023

#Excellent catch @robbiejackson

avatar brianteeman
brianteeman - comment - 10 Jan 2023

Fairly certain that this cannot be changed or it will break backwards compatibility. @laoneo is that correct?

avatar HLeithner
HLeithner - comment - 10 Jan 2023

@brianteeman can you please stop reporting every comment of @wojtekxtx it's really offending against maintainers

avatar laoneo
laoneo - comment - 10 Jan 2023

Fairly certain that this cannot be changed or it will break backwards compatibility. @laoneo is that correct?

It can, when the old name is deprecated for 6.0.

avatar wojtekxtx
wojtekxtx - comment - 10 Jan 2023

@laoneo is there somewhere (early) roadmap for 6.0 or is it too early for this?

avatar robbiejackson
robbiejackson - comment - 10 Jan 2023

I was thinking that one possibility would be to add a new function into the trait, one that had the name you wanted to use long term. Then mark the other one as deprecated, to be removed in some release. That way 3rd party developers would have some warning that it would disappear, and new developments could use the right name from the outset.

It would be ugly for a while, but would enable you to end up with a tidy solution


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/39575.

avatar laoneo
laoneo - comment - 11 Jan 2023

@laoneo is there somewhere (early) roadmap for 6.0 or is it too early for this?

No there isn't. But our updated deprecation policy demands, that we have to add deprecations for the for the over next major release. So when you deprecate something in a 4 minor release, then the earliest release is 6.0 where it is planned to get removed. This gives extension developers enough time to update their extensions, especially as we have now timed releases, where a new major will come out every two years.

avatar Hackwar Hackwar - change - 23 Feb 2023
Labels Added: bug
avatar Hackwar Hackwar - labeled - 23 Feb 2023

Add a Comment

Login with GitHub to post a comment