On Mon, 22 Apr 2019 at 11:21, Christian Grün <christian.gruen@gmail.com> wrote:

That’s good to know. Once we decide to stabilize our profiling and debugging features and make them public, we’ll have a closer look into the tracing API of Saxon.

Great.

Thanks
Christian

PS: Our team member Sabine extended our Wiki article on the integration of IntelliJ. She might soon give you some feedback on her experiences with BaseX and your plugin.

That would be useful.

NOTE: In version 1.4 it is now possible to select "Active editor file" as the query to run, and specify a context item (currently strings only). I have also changed the output to put the item information into a separate table (see https://plugins.jetbrains.com/files/8612/screenshot_19185.png).

Some of the things I am thinking about for the run configurations are:

1. Supporting variables/parameters.

2. Supporting specifying the type of the context item and variables.

3. Highlighting single result items according to the resulting mimetype (text, xml, json, html, rdf, etc.).

4. Support for viewing csv, json, etc. results in a tabular form in addition to the text output.

5. Supporting saving the output to a file, with an option to open the result in IntelliJ, a web browser, or some other application.

6. Providing the ability to edit BaseX configuration files from within the plugin with a UI specific to the BaseX configuration structure.

7. Support navigating from the query error stack trace to the file that caused the error.

Some other things I am thinking about are:

1. An IntelliJ inspection to validate XQuery files using the query processor (e.g. using BaseX's xquery:parse API).

2. Log viewer integration for admin:logs.

3. Unit test integration (IntelliJ test view for the unit module).

4. Documentation integration, xqDoc syntax validation, and support for BaseX xqDoc generation via the inspection module.

5. Database navigation (list the database contents, view/add/edit/delete files, view file properties).

Kind regards,

Reece