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

What about provide plugin for debugging content #116

Open
VereschakSun opened this issue Oct 15, 2019 · 1 comment
Open

What about provide plugin for debugging content #116

VereschakSun opened this issue Oct 15, 2019 · 1 comment

Comments

@VereschakSun
Copy link

VereschakSun commented Oct 15, 2019

Hi. I have some trouble when use this plugin
I use webstorm/phpstorm/
When I wrote table like this. My qa manager must to check all thead's in translate file. It;s too long and not comfortably.
I think will be grate if you create some plugin or something else for show correct translates for this case.
Thank you!

                    <thead>
                    <tr>
                        <th></th>
                        <th>{{$t('thead1')}}</th>
                        <th>{{$t('thead2')}}</th>
                        <th>{{$t('thead3')}}</th>
                        <th>{{$t('thead4')}}</th>
                        <th>{{$t('thead5')}}</th>
                    </tr>
                    </thead>
                   <tbody>....</tbody>
@tikiatua
Copy link
Member

Hi @VereschakSun

Thank you for your input. I am absolutely on the same page with you. It is not only tedious for the qa manager but I think also for the developer who needs to manage all the translations.

Writing a plugin for a specific IDE (i.e web storm) is one solution, although we would probably first tackle visual studio code instead of web storm. However, we are currently exploring the use of a specific linter command that would automatically check all translation strings as well as a special frontend plugin, that would allow to explore and adapt translations directly in the user interface.

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

No branches or pull requests

2 participants