Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Laminas\Translator #128

Merged
merged 2 commits into from
Jul 2, 2024
Merged

Conversation

gsteel
Copy link
Member

@gsteel gsteel commented Jul 1, 2024

Q A
New Feature yes

Description

Requires laminas/laminas-translator and extends the shipped interface via Laminas\I18n\Translator\TranslatorInterface

As a straight copy of the existing interface, there's no BC break, but I guess there is a "technical" BC break because of any change in inheritance.

If this has to go into a major release, it defeats the point of extracting the interface in the first place.

Requires `laminas/laminas-translator` and extends the shipped interface via `Laminas\I18n\Translator\TranslatorInterface`

Signed-off-by: George Steel <george@net-glue.co.uk>
@gsteel gsteel added this to the 2.27.0 milestone Jul 1, 2024
@gsteel gsteel requested a review from a team July 1, 2024 21:59
… `laminas/laminas-translator`

Signed-off-by: George Steel <george@net-glue.co.uk>
@boesing
Copy link
Member

boesing commented Jul 2, 2024

AFAIR just having an Interface extending another is not a bc break. 🤔
doctrine did this plenty of times.

@asgrim
Copy link
Member

asgrim commented Jul 2, 2024

AFAIR just having an Interface extending another is not a bc break. 🤔 doctrine did this plenty of times.

yep, it's only a BC break if the new parent interface adds new methods that weren't there before 👍

@gsteel gsteel self-assigned this Jul 2, 2024
@gsteel gsteel merged commit f09a48c into laminas:2.27.x Jul 2, 2024
12 checks passed
@gsteel gsteel deleted the require-laminas-translator branch July 2, 2024 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants