-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Should handle resources/views/vendor/$package/ and resources/lang/vendor/$package/lang.json #44
Comments
The workaround that worked at least to have the views, but is kinda fiddly has been:
done |
on that journey another fine option would be to specify only a source lang.json and to skip the whole file reader work that parses views and controllers .. maybe as a Console Command flag |
The problem here is that it ignores any(?) directory named "vendor" |
…/lang/vendor//lang.json
There's a security issue here that needs to be applied immediately 0777 permission is too open |
Is there any workaround using php files? |
you can use my PR here #44 (comment) |
@itsrexb Does it work with the |
proposed outcome
additional notes
laravel doc suggests to publish vendor packages to resources/lang/vendor/$vendor/lang.json
translations genarated by
laravel-google-translate
that have been read from `resources/vendor/$package/lang.json should also be written to this target.now only lang/lang.json is supported and used
JsonArrayFileTranslator.php#L46
The text was updated successfully, but these errors were encountered: