Few things to know about the extension

its a test :) excuse the nested if statements
all the parser does is pick up the docTitle content from two different xmls files - 01-01_instanz_01_regelungstext.xml and 01-01_instanz_01_vorblatt.xml.
for the interactive clicking part I hardcoded the positional information (the column and line number) so only one file when open will take you to the correct position 01-01_instanz_01_vorblatt.xml.
I learned that the xml2js package does not retain positional information. For that we need a different packaage like sax-js then we can dynamically add the column and line numbers to each piece of content.

How to run

Add the two xml files - 01-01_instanz_01_regelungstext.xml and 01-01_instanz_01_vorblatt.xml to the workspace. You can find links to them in the Re-discovery miro board in the frame titled Add outline view Extension.
The table of contents view panel should open as it detects an xml and you should see text representing the docTitle

Everything below here is boilerplate readme

Features

Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.

For example if there is an image subfolder under your extension project workspace:

![feature X](images/feature-x.png)

Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.

Requirements

If you have any requirements or dependencies, add a section describing those and how to install and configure them.

Extension Settings

Include if your extension adds any VS Code settings through the contributes.configuration extension point.

For example:

This extension contributes the following settings:

myExtension.enable: Enable/disable this extension.
myExtension.thing: Set to blah to do something.

Known Issues

Calling out known issues can help limit users opening duplicate issues against your extension.

Release Notes

Users appreciate release notes as you update your extension.

1.0.0

Initial release of ...

1.0.1

Fixed issue #.

1.1.0

Added features X, Y, and Z.

Following extension guidelines

Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.

Extension Guidelines

Working with Markdown

You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:

Split the editor (Cmd+\ on macOS or Ctrl+\ on Windows and Linux).
Toggle preview (Shift+Cmd+V on macOS or Shift+Ctrl+V on Windows and Linux).
Press Ctrl+Space (Windows, Linux, macOS) to see a list of Markdown snippets.

For more information

Enjoy!

hamo225 / extension_custom_view