We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you for cool package. I applied this package to my project and the result is very good.
Except one thing that package scans only *.php and *.vue.
*.php
*.vue
How about the functionality which allows user can manually add files or directories to scan? something like...
# config/translation.php ... 'extra_files' => [ resource_path('js/something.js'), resource_path('scripts/*.js'), ], ...
I thought that it would be very convenient if this kind of functionality is available.
Thank You.
The text was updated successfully, but these errors were encountered:
Thanks for your suggestion. Will it solve your issue if we extended the config to have extensions selection?
# config/translation.php ... 'extensions' => ['*.php', '*.vue'], ...
That way you are able to get the scanner du handle .js files as well.
Sorry, something went wrong.
If I have multiple js files in single folder, can I scan only handle.js?
js
handle.js
/resources /js /handle.js /somthing.js /else.js /foobar.js
It could properly be made, but why would you exclude files from scanning?
Added release 1.0.6 where you can select which extensions the scanner scans for.
No branches or pull requests
Thank you for cool package.
I applied this package to my project and the result is very good.
Except one thing that package scans only
*.php
and*.vue
.How about the functionality which allows user can manually add files or directories to scan?
something like...
I thought that it would be very convenient if this kind of functionality is available.
Thank You.
The text was updated successfully, but these errors were encountered: