A repeated query key is not necessarily a duplicate to discard. QueryNest connects a Windows project folder to an AI conversation so you can inspect ordered query pairs, empty values and the encoding of a literal plus sign.
import re
from urllib.parse import parse_qsl, urlencode
def append_query(query, key, value):
if any(type(x) is not str for x in (query, key, value)):
raise ValueError("query.type")
if re.search(r"%(?![0-9A-Fa-f]{2})", query):
raise ValueError("query.escape")
pairs = parse_qsl(query, keep_blank_values=True,
strict_parsing=True, errors="strict", max_num_fields=1000)
return urlencode([*pairs, (key, value)])Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Base URL, credentials and a reachable server.
Distinguish a literal plus encoded as %2B from a space and reject malformed percent escapes or invalid UTF-8.
import re
from urllib.parse import parse_qsl, urlencode
def append_query(query, key, value):
if any(type(x) is not str for x in (query, key, value)):
raise ValueError("query.type")
if re.search(r"%(?![0-9A-Fa-f]{2})", query):
raise ValueError("query.escape")
pairs = parse_qsl(query, keep_blank_values=True,
strict_parsing=True, errors="strict", max_num_fields=1000)
return urlencode([*pairs, (key, value)])QueryNest is a Windows AI coding workspace for developers who need to change request-building code without losing the meaning of its inputs. Select your project folder and describe which query values must survive a change. Ask the connected assistant to inspect both parsing and serialization, including callers that depend on order, empty fields or repeated names. This turns a string edit into a reviewable application task.
In the query_pairs.py example, appending a pair raises questions about existing blank values and malformed escapes. You can use that context to examine a similar helper in your own project. QueryNest does not supply a URL-processing service; the example illustrates code to discuss and verify. Review the proposal against the data your application accepts instead of assuming that converting everything to a dictionary preserves the request.
Then run your project checks on ordinary queries and the cases that distinguish the old behavior from the intended one. Inspect the serialized result as well as what the consumer reads from it. QueryNest connects to supported OpenAI-compatible or Anthropic endpoints with credentials where needed. An unfiltered model may be selected when offered, but provider restrictions still apply and the server determines tools and context. Your request contract remains the basis for accepting code.
A request can contain more than one pair with the same name, and a consumer may rely on those values. Tell the assistant whether to retain them and inspect any proposed data structure that could discard them.
Not necessarily. Your application may interpret an empty field differently from one that was never supplied. Include both cases in the task and check the parser and serializer together before deciding that their behavior is interchangeable.
The example is a development workflow, not an automatic validation gateway. You review and test your own helper code in the project. Its accepted URL forms and rejection behavior need to be defined by your application.
Check whether the consumer reads the same values and whether exact serialization matters to your integration. Equivalent-looking text may still affect signatures or comparisons, so state those dependencies before accepting a normalization change.
QueryNest · Updated 2026-10-25