Is your feature request related to a problem? Please describe.

Running the code below will result in two different error messages:

xquery version "3.1";

try { [1,2,3,4](-1) } catch err:FOAY0001 { $err:description },
try { array:get([1,2,3,4], -1) } catch err:FOAY0001 { $err:description }

• "Array index out of bounds. Position -1 does not exist in this array. Length

From @Frederic-P in eXist-db/documentation#231 (comment):

There should be at least a link referencing the documentation of eXide where users are informed about. The current reference material (at http://exist-db.org/exist/apps/eXide/docs/doc.html and https://exist-db.org/exist/apps/doc/learning-xquery.xml) do not cover the following things:

1. The

Add support for running MarkLogic Roxy/Unit tests.

• processor.test -- API
• processor.impl.roxy.test -- https://github.com/marklogic-community/roxy
• processor.impl.roxy.test -- https://github.com/marklogic-community/marklogic-unit-test

NOTE: Both roxy and marklogic-unit-test provide the same test API.

A toolbar (https://atom.io/packages/tool-bar) with buttons for common functions like "Run XQuery" and "Toggle Database View" would be useful.

A toolbar could also be used to expose commands that are currently inaccessible, like "Previous" or "Next" for paging through query results (which are currently chopped off at 10 with no means to see 11+), serialization method (currently hard coded as ad

According to http://exist-db.org/exist/apps/demo/examples/special/i18n-docs.html#configuration, also https://github.com/eXist-db/demo-apps/blob/master/examples/special/i18n-docs.html#L112 (see other locations on this page...), i18n.xql is located in /db/i18n/modules/i18n.xql. It is actually in /db/apps/demo/modules/i18n.xq - see https://github.com/eXist-db/demo-apps/blob/master/modules/i18n.

As originally reported by @duncdrum at eXist-db/function-documentation#21.

Without xqdoc documentation, the function documentation for the app.xql module as shown at http://exist-db.org/exist/apps/fundocs/view.html?uri=http://exist-db.org/xquery/app&location=/db/apps/public-repo/modules/app.xql&details=true is not particularly useful.

Currently we can deploy a package as an app or lib expath package. In practice we often also have pure data apps to decouple development of apps from their data.

Should be rather easy to add a new type to be configured in repo.xml like

<type>data</type>

Before eXist-db/exist#2991 - or respectively eXist-db/exist#3227 - is merged:

https://exist-db.org/exist/apps/doc/lucene, the article covering the integration of Lucene in exist-db, should be extended with a section.
It should describe one or two use-cases for having one analyzer for indexing and another to analyze the query.

why not simply action="index.html"❓
the login form action attribute is generated by the function app:form-action-to-current-url in app.xql. This function returns the request:get-url(). behind a proxy (in my case apache mod_proxy, that does not rewrite the request header) it guides to any localhost:port location, whil