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

Consider making the I18n class private #2927

Closed
2 tasks done
colinrotherham opened this issue Oct 18, 2022 · 1 comment · Fixed by #2941
Closed
2 tasks done

Consider making the I18n class private #2927

colinrotherham opened this issue Oct 18, 2022 · 1 comment · Fixed by #2941

Comments

@colinrotherham
Copy link
Contributor

colinrotherham commented Oct 18, 2022

What

Do we want to consider I18n "private" whilst we continue changing, refactoring, improving?

We've already noted in #2926 that we may rename our I18n class

Why

Making features "public" means we can't make breaking changes without major releases
Making features "private" (or for internal use) means we're relatively free to make changes where needed

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

  • Decision made on private versus public
  • Change made in code to remove GOVUKFrontend.I18n from govuk/all.js
@romaricpascal
Copy link
Member

Concensus at the meeting was to keep it private for now and possibly open it up in a future release, so opened up #2941 to deal with it 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants