Skip to content
This repository was archived by the owner on May 5, 2024. It is now read-only.

Creating a translation class which enables the usage of translated error messages#70

Open
ghost wants to merge 1 commit intodevelopfrom
unknown repository
Open

Creating a translation class which enables the usage of translated error messages#70
ghost wants to merge 1 commit intodevelopfrom
unknown repository

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Oct 12, 2015

  • created the \Upload\Translation class
  • created the folder src/Upload/Language with 2 files: en.php and pt-BR.php
  • the language files returns an array with messages as key / value
  • the message keys are the original messages used in the project, so if the user
    decides to not use the validation class, it won't affect the behavior
  • added a TranslationTest class
  • added additional tests to existent test classes
  • updated the README.md to display usage of the translation class
  • added aditional methods to use the translation inside existing classes and because
    the project still gives support to PHP 5.3, trait usage was avoided

…ror messages

- created the \Upload\Translation class
- created the folder src/Upload/Language with 2 files: en.php and pt-BR.php
- the language files returns an array with messages as key / value
- the message keys are the original messages used in the project, so if the user
  decides to not use the validation class, it won't affect the behavior
- added a TranslationTest class
- added additional tests to existent test classes
- updated the README.md to display usage of the translation class
- added aditional methods to use the translation inside existing classes and because
  the project still gives support to PHP 5.3, trait usage was avoided
@ghost
Copy link
Copy Markdown
Author

ghost commented Oct 12, 2015

Brandon, I run the test using PHPUnit and all tests passed here.
I think you're missing a .travis.yml in the development branch.

@scottrobertson
Copy link
Copy Markdown
Contributor

@ramirovjr the develop branch is about 3 years out of date, it should really be removed. Can you retarget this at master?

@ghost
Copy link
Copy Markdown
Author

ghost commented Oct 12, 2015

Yes, just need to fix the conflicts.
It will be done until the end of the day.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants