Location of Schema used for current xml file unclear
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
Research direction
The report points to the View/Schemas dialog, schema resolution, auto-completion, and on-the-fly verification; no source files or tests are named. Start by tracing how XML Notepad selects the schema for an ARXML document. Done means the requested schema can be supplied explicitly and the exact active schema file is visible to users.
Written by the indexing model from the issue text.
Description
I am working with a standard that has quite a few revisions of its Schema: AUTOSAR (autosar.org)
When opening an ARXML file in XML Notepad the tool shows me the auto completion and does on-the-fly verification.
However, it is not clear to me which exact schemal version i.e. xsd file XML Notepad is using: While I see one version in the View/Schemas... dialog, this is sometimes clearly not the revision of the schema that is used internally: the two schema revisions have different elements, and I get elements in the auto-completion for my xml file that are not present in the schema revision that is indicated in the View/Schemas dialog).
Is XML Notepad buffering schemas in the background, or pulling them from the registry or something like this? If yes, what is the logic behind this?
In particular it would be good if XML Notepad would support the following use cases:
(1) I want to provide XML Notepad with the exact schema file I want to use when editing an xml file.
(2) I want to have an indication somewhere in the program of which exact schema file is currently being using.
Thank you for this tool. I have been using it for years, and I am generally very happy with it. However, the schema issue described keeps giving me trouble.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 microsoft/XmlNotepad
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/XmlNotepad#532 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/XmlNotepad#517 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/XmlNotepad#500 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/XmlNotepad#499 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
microsoft/XmlNotepad#495 · 1 comment ·
All issues in microsoft/XmlNotepad
Similar issues
-
untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/dotnet-api-docs#13095 ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
newrelic/newrelic-dotnet-agent#3850 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
LuckyPennySoftware/AutoMapper#4660 ·