Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Eliminate necessity for the extensions to depend on the IDE App module
See original GitHub issueThere are about 30 IDE extensions, in the CHE/Codenvy assemblies, which must depend on the IDE App (che-core-ide-app module) in order to use just a few interfaces/classes. Like org.eclipse.che.ide.CoreLocalizationConstant,
org.eclipse.che.ide.newresource.AbstractNewResourceAction, etc. Having a such dependency really is a bad practice for the IDE extensions.
The goal of this task is to eliminate the necessity for the IDE extensions to depend on the che-core-ide-app module. This may require moving some interfaces/classes from che-core-ide-app to che-core-ide-api or improve IDE API in some way.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@azatsarynnyy @vparfonov Let’s review and try to find a “golden mean” (not putting a lot of effort). Indeed, let’s do not consider a “refactoring” but be dependent on other module just due to a couple of constants does not look that reasonable. Thoughts?
Closing as Che 6 editor is no longer under active development