Opting out for specific known content types
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the linked PDE #294 and LemMinx #1275 discussions to understand the boundary between Wild Web Developer and LemMinx. Identify where Wild Web Developer handles content types and validation, then define the completion criteria as suppressing schema-related warnings for the listed PDE resources without disabling validation for other XML files.
Written by the indexing model from the issue text.
Description
There should be a way to opt of validation for specific know content types.
The issue arises relates to this issue raised for PDE:
https://github.com/eclipse-pde/eclipse.pde/issues/294
PDE has abused the XML Schema namespace for its own purpose leading to all kinds of validation errors that are not really errors for PDE's actual use of *.exsd resources.
Similarly a PDE *.target file doesn't specify a schema, but the editor knows the correct structure so a warning about the schema being missing is just noise to the user. Same for feature.xml, category.xml, plugin.xml, and *.product.
The Lemminx functionality is generally very cool and very useful, but it seems the only way to disable this for PDE's resources is to disable it in general, which definitely not desired either. Apparently the issue should not be addressed in LemMinx, as suggested by this comment:
https://github.com/eclipse-pde/eclipse.pde/issues/294#issuecomment-1216550919
but rather in Wild Web Developer as suggested by this comment:
https://github.com/eclipse/lemminx/issues/1275#issuecomment-1221371932
- Dominant language
- Java
- Stars
- 203
- Forks
- 76
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-wildwebdeveloper/wildwebdeveloper
-
Markdown and Astro language servers do not start when the project path contains a non-ASCII character or a spacePossibly taken @RoiSoleil claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eclipse-wildwebdeveloper/wildwebdeveloper#2277 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
eclipse-wildwebdeveloper/wildwebdeveloper#2236 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
eclipse-wildwebdeveloper/wildwebdeveloper#2177 ·
Maintainers usually reply within 1 day
-
SQL Language serverOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
eclipse-wildwebdeveloper/wildwebdeveloper#2122 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-wildwebdeveloper/wildwebdeveloper#2070 · 1 comment ·
Maintainers usually reply within 1 day
All issues in eclipse-wildwebdeveloper/wildwebdeveloper
Similar issues
-
面渣逆袭Spring事务传播机制勘误Open
Difficulty 1/5 Under an hour Newbie friendliness 80/100
itwanger/toBeBetterJavaer#218 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
johanhaleby/occurrent#1462 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
SasanLabs/VulnerableApp#912 ·
Maintainers usually reply within 1 day
-
area/build area/events area/storage area/storage/kafkasql area/storage/sql
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Apicurio/apicurio-registry#11079 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenAEV-Platform/openaev#9139 ·
Maintainers usually reply within 1 day