[Suggestion] Ignore DS137138 in xml documentation and xml namespaces
See original GitHub issueSo far I am happy with the plugin, but most of the time I am ignoring errors for web pages that are mentioned in the xml docu or xml namespace (which btw. kills visual studio 2015). It would be nice if there would be an option to ignore links in the xml docu like:
/// <para tool="javadoc-to-mdoc"> /// <format type="text/html"> /// <a href="http://developer.android.com/reference/android/app/Activity.html#onStop()" target="_blank">[Android Documentation]</a> /// </format> /// </para>
Bg
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:22 (12 by maintainers)
Top Results From Across the Web
how to ignore xml namespaces?
When I'm trying to deserialize, everything works fine. But the problem is that sometimes the structure of this xml file is different -...
Read more >XML Namespaces
In XML, element names are defined by the developer. This often results in a conflict when trying to mix XML documents from different...
Read more >Namespaces in XML 1.0 (Third Edition)
XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating ...
Read more >XML Schema: Understanding Namespaces
Moving to XML Schema? This introduction to namespaces will help you understand one of its more important elements.
Read more >Managing Namespaces in an XML Document
Learn how to manage namespaces in an XML document. XML namespaces associate element and attribute names in an XML document with custom and ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, all the effort went to Command Line Tool and making rules better. The VS 2017 extension will be updated next.
@PavelBansky, I think option 1 makes more sense, as the entry level for this extension should be as low as possible to make its reach as broad as possible.