Support user override lang folders

[asika32764]

CronTranslator::parse('@weekly', 'pt')
                ->addLangDir(__DIR__ . '/my/custom/lang')
                ->translate();

// OR

CronTranslator::parse('@weekly')
                ->addLangDir(__DIR__ . '/my/custom/lang')
                ->translate('pt', true);

To keep B/C, I expose CronExpression class that user can configure it. I decided not to add 4th params to translate() method.

CronTranslator class added 2 new public methods

$expr = CronTranslator::parse($cron, $lang, $24hour); // To create a new CronExpression

// Configure it

CronTranslator::translateExpression($expr); // Return translated string

// Old way still works
CronTranslator::translate('cron', 'en', true); // Works

[lorisleiva]

Hi there, thanks for this. I like the idea of this PR but I'm not a big fan of pushing all the logic from the CronTranslator to the CronExpression. It feels like these directories should probably be stored on the CronTranslator instead but that may require a bit of refactoring first.

[asika32764]

Yes, I see what you want.

I push all logic to CronExpression just because I want to keep B/C and avoid too large rewrite of whole project.

If you have new idea about how to implement this, fell free to take my code to rewrite it.

Just depends on your disicion.

[lorisleiva]

I'm closing this because PR #42 adds a new LanguageLoader class which could be used to support language folder overrides if you'd like to give it a go. 🙂