You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The org.eclipse.cdt.lsp.examples.preferences project demonstrates how to override the "normal" flow of CDT-LSP, in particular it hides the CDT LSP preference page settings. This is useful for extenders who want to force settings or provide their own settings page. See the javadoc on ConfigurationVisibility for more information on that.
The problem is that if a CDT developer/contributor imports all projects into the Eclipse workspace the behaviour changes means that the default flow as outlined in the readme no longer work.
We already recommend closing the projects for manual setup -
4. Consider closing the `org.eclipse.cdt.lsp.examples.*` projects as they demonstrate how to extend CDT LSP and may affect the overall behaviour, for example by removing the "Prefer C/C++ Editor (LSP)" checkbox.
This issue is to apply this automatically to the oomph configuration, either by closing the project after import, or not importing the project at all.
The text was updated successfully, but these errors were encountered:
The org.eclipse.cdt.lsp.examples.preferences project demonstrates how to override the "normal" flow of CDT-LSP, in particular it hides the CDT LSP preference page settings. This is useful for extenders who want to force settings or provide their own settings page. See the javadoc on ConfigurationVisibility for more information on that.
The problem is that if a CDT developer/contributor imports all projects into the Eclipse workspace the behaviour changes means that the default flow as outlined in the readme no longer work.
We already recommend closing the projects for manual setup -
cdt-lsp/CONTRIBUTING.md
Line 15 in dd79754
This issue is to apply this automatically to the oomph configuration, either by closing the project after import, or not importing the project at all.
The text was updated successfully, but these errors were encountered: