Tools

submit_feedback

Tell the people who build LexLint what went wrong.

What it does

It writes your feedback on LexLint to the people who build it, recorded against your UnGovr account so we can write back. Arguments: comments (required), usage_summary, client, plugin_version.

An agent should call it only when you ask it to, and send only what you have explicitly approved. It should draft the usage summary from what it actually did, show you the exact payload, and send that and nothing else. It should never read your session transcript to build one: if you have pasted a key into a session, it is recorded there. Running it is your decision every time. One other thing is sent automatically and it is the whole of the rest of the list: which plugin version you are running, forwarded with the check_access preflight and stored on its own, in a place that holds nothing but version numbers. It tells us whether anyone is still on a bundle old enough that retiring a tool name would break them. A version string and nothing else, with no record of what you linted. Nothing else about your sessions is collected automatically by LexLint. Your key is an UnGovr Open Data key, and that API keeps a request log of its own, set out at https://www.ungovr.org/open-data/api-keys and holding which collection was asked for and a one-way hash of the key, never which jurisdiction you looked up.

It is deliberately not runnable from the console. A Run button on a page you are poking at would file real feedback against your account as a side effect of exploring, and the whole point of the tool is that you approved the text first.

Parameters