@adminforth/agent 1.50.0 → 1.50.1
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.
package/build.log
CHANGED
|
@@ -62,5 +62,5 @@ custom/speech_recognition_frontend/voiceActivityDetection.ts
|
|
|
62
62
|
custom/speech_recognition_frontend/types/
|
|
63
63
|
custom/speech_recognition_frontend/types/voice-activity-detection.d.ts
|
|
64
64
|
|
|
65
|
-
sent 1,670,
|
|
66
|
-
total size is 1,666,
|
|
65
|
+
sent 1,670,943 bytes received 921 bytes 3,343,728.00 bytes/sec
|
|
66
|
+
total size is 1,666,790 speedup is 1.00
|
|
@@ -24,6 +24,8 @@ If several rows look similar, do not guess which one is "the same" record. Show
|
|
|
24
24
|
|
|
25
25
|
For long texts show only several first words and add "..." at the end (only if user did not request this field specifically).
|
|
26
26
|
|
|
27
|
+
Never show information about more than 10 records in one message. If a tool returns more than 10 relevant records, summarize the total count if known, show only the 10 most relevant records, and offer to narrow filters, sort differently, or continue with the next 10.
|
|
28
|
+
|
|
27
29
|
Also when you communicate with user about record, add related link to this record. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
|
|
28
30
|
|
|
29
31
|
Before sending the link, verify that the `resourceId`, `{primary key}`, `_label`, and shown fields come from the same exact returned row.
|
|
@@ -27,6 +27,8 @@ Also please add related link to record with will be changed. Build it as `{ADMIN
|
|
|
27
27
|
|
|
28
28
|
Before sending the confirmation, verify that the `resourceId`, `{primary key}`, `_label`, and all shown fields come from the same exact fetched row.
|
|
29
29
|
|
|
30
|
+
Never show information about more than 10 records in one message. If a mutation plan affects more than 10 records, show only the 10 most important examples plus the total count if known, and ask the user to confirm the clearly described full batch.
|
|
31
|
+
|
|
30
32
|
And in the same message ask user for final confirmation.
|
|
31
33
|
|
|
32
34
|
When creating new record, show user all data which you gona create and in same message ask for confirmation.
|
|
@@ -123,6 +125,8 @@ For decimal fields please use string values with dot as decimal separator.
|
|
|
123
125
|
|
|
124
126
|
After creation of new record also show user a link to this record. If several records record were created, show links to all of them in list.
|
|
125
127
|
|
|
128
|
+
If more than 10 records were created, show links or details for only 10 of them and summarize the remaining count.
|
|
129
|
+
|
|
126
130
|
Omit any pictures or file paths, you are not capable of doing it. If they are not required all is good, if they are required, explain to user that you are not able to create record because of this reason.
|
|
127
131
|
|
|
128
132
|
### Working with dates
|
|
@@ -24,6 +24,8 @@ If several rows look similar, do not guess which one is "the same" record. Show
|
|
|
24
24
|
|
|
25
25
|
For long texts show only several first words and add "..." at the end (only if user did not request this field specifically).
|
|
26
26
|
|
|
27
|
+
Never show information about more than 10 records in one message. If a tool returns more than 10 relevant records, summarize the total count if known, show only the 10 most relevant records, and offer to narrow filters, sort differently, or continue with the next 10.
|
|
28
|
+
|
|
27
29
|
Also when you communicate with user about record, add related link to this record. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
|
|
28
30
|
|
|
29
31
|
Before sending the link, verify that the `resourceId`, `{primary key}`, `_label`, and shown fields come from the same exact returned row.
|
|
@@ -27,6 +27,8 @@ Also please add related link to record with will be changed. Build it as `{ADMIN
|
|
|
27
27
|
|
|
28
28
|
Before sending the confirmation, verify that the `resourceId`, `{primary key}`, `_label`, and all shown fields come from the same exact fetched row.
|
|
29
29
|
|
|
30
|
+
Never show information about more than 10 records in one message. If a mutation plan affects more than 10 records, show only the 10 most important examples plus the total count if known, and ask the user to confirm the clearly described full batch.
|
|
31
|
+
|
|
30
32
|
And in the same message ask user for final confirmation.
|
|
31
33
|
|
|
32
34
|
When creating new record, show user all data which you gona create and in same message ask for confirmation.
|
|
@@ -123,6 +125,8 @@ For decimal fields please use string values with dot as decimal separator.
|
|
|
123
125
|
|
|
124
126
|
After creation of new record also show user a link to this record. If several records record were created, show links to all of them in list.
|
|
125
127
|
|
|
128
|
+
If more than 10 records were created, show links or details for only 10 of them and summarize the remaining count.
|
|
129
|
+
|
|
126
130
|
Omit any pictures or file paths, you are not capable of doing it. If they are not required all is good, if they are required, explain to user that you are not able to create record because of this reason.
|
|
127
131
|
|
|
128
132
|
### Working with dates
|