@xano/xanoscript-language-server 12.19.0 → 12.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -446,6 +446,8 @@ api.call "account/{account_id}" verb=POST {
446
446
 
447
447
  Calls an internal Xano API endpoint from within a `workflow_test` or `test` clause. This allows you to invoke internal APIs as part of your end-to-end workflow tests or unit tests within queries, functions, and tasks.
448
448
 
449
+ To call the endpoint as a logged-in user, pass a token with `auth = {token: "...", ignore_expiration: true}` (a literal token) or an `Authorization` header (`headers = ["Authorization: Bearer " ~ $token]`).
450
+
449
451
  # trigger.call
450
452
 
451
453
  ```xs
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xano/xanoscript-language-server",
3
- "version": "12.19.0",
3
+ "version": "12.20.0",
4
4
  "description": "Language Server Protocol implementation for XanoScript",
5
5
  "type": "module",
6
6
  "main": "server.js",
@@ -56,6 +56,10 @@ export function apiCallFn($) {
56
56
  fnToken,
57
57
  {
58
58
  api_group: "[string]",
59
+ // The endpoint's credential, as the server's transform reads it:
60
+ // a literal token (the parser refuses a computed one; use an
61
+ // Authorization header for that), and ignore_expiration.
62
+ "auth?": { token: "[string]", "ignore_expiration?": "[boolean]" },
59
63
  "description?": "[string]",
60
64
  "disabled?": "[boolean]",
61
65
  "headers?": "[expression]",
@@ -2,7 +2,7 @@
2
2
  * The policy check catalogue the language server validates policies against.
3
3
  *
4
4
  * The platform owns the catalogue: `GET workspace/{id}/policy/check` (and `xano policy
5
- * catalogue -o json`) answers `{items: [check...], goals, document}`: each check with its id,
5
+ * catalogue -o json`) answers `{items: [check...], templates, document}`: each check with its id,
6
6
  * label, description and param schemas, and `document`, the policy file's own fields (their types,
7
7
  * value sets and defaults, retired fields, reserved blocks, the key pattern). Nothing here writes a
8
8
  * check or a field down by hand. The registry starts EMPTY, and an empty registry means the