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
Currently, KJSencha isn't really friendly with the Sencha CLI.
That's because AssetManager splits JS files all over the modules in a manner that is hard to track.
A solution may be to crawl assets, copy them into a library and then run Sencha CLI there.
Still not sure about the best approach though.
ping @fduarte42
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, KJSencha isn't really friendly with the Sencha CLI.
That's because AssetManager splits JS files all over the modules in a manner that is hard to track.
A solution may be to crawl assets, copy them into a library and then run Sencha CLI there.
Still not sure about the best approach though.
ping @fduarte42
The text was updated successfully, but these errors were encountered: