In an empty instance with nothing but the api installed, no restxq tree item is displayed. In a normal install with default apps it is there.

With api version 1.2.0 and exist 5.4.0-SNAPSHOT the shortened response looks like this.
[ {
"uri" : "/fusiondb/group",
"methods" : [ {
"name" : "GET",
"function" : {
"src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm",
"name" : "list-groups#0"
}
} ]
}, {
"uri" : "/fusiondb/collection",
"methods" : [ {
"name" : "POST",
"function" : {
"src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm",
"name" : "update-collection-properties#2"
}
}, {
"name" : "DELETE",
"function" : {
"src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm",
"name" : "delete-collection#1"
}
},
( … )
{
"uri" : "/",
"methods" : [ {
"name" : "",
"function" : {
"src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm",
"name" : "explorerOptions#0"
}
} ]
} ]
Not yet sure why these wouldn't be displayed, but obviously this accounts for the failing tests on CI checking for the display of restxq functions.
maybe the fact that this is an array of length 1 is a problem see api and extensions
but so far i haven't seen any filters that would exclude the API itself from being displayed in the restxq tree menu.
see #219
In an empty instance with nothing but the api installed, no restxq tree item is displayed. In a normal install with default apps it is there.
With api version
1.2.0and exist5.4.0-SNAPSHOTthe shortened response looks like this.[ { "uri" : "/fusiondb/group", "methods" : [ { "name" : "GET", "function" : { "src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm", "name" : "list-groups#0" } } ] }, { "uri" : "/fusiondb/collection", "methods" : [ { "name" : "POST", "function" : { "src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm", "name" : "update-collection-properties#2" } }, { "name" : "DELETE", "function" : { "src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm", "name" : "delete-collection#1" } }, ( … ) { "uri" : "/", "methods" : [ { "name" : "", "function" : { "src" : "/db/system/repo/fusion-studio-api-1.2.0/api.xqm", "name" : "explorerOptions#0" } } ] } ]Not yet sure why these wouldn't be displayed, but obviously this accounts for the failing tests on CI checking for the display of restxq functions.
maybe the fact that this is an array of length
1is a problem see api and extensionsbut so far i haven't seen any filters that would exclude the API itself from being displayed in the restxq tree menu.
see #219