Software / code / prosody
File
spec/util_jsonpointer_spec.lua @ 13762:81856814d74f 13.0
util.argparse: Fix bug (regression?) in argument parsing with --foo=bar
After recent changes, '--foo bar' was working, but '--foo=bar' was not. The
test had a typo (?) (bar != baz) and because util.argparse is not strict by
default, the typo was not caught.
The typo caused the code to take a different path, and bypassed the buggy
handling of --foo=bar options.
I've preserved the existing test (typo and all!) because it's still an
interesting test, and ensures no unintended behaviour changes compared to the
old code.
However I've added a new variant of the test, with strict mode enabled and the
typo fixed. This test failed due to the bug, and this commit introduces a fix.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 11 Mar 2025 18:27:36 +0000 |
| parent | 12777:4d5549de27e6 |
line wrap: on
line source
describe("util.jsonpointer", function() local json, jp; setup(function() json = require "util.json"; jp = require "util.jsonpointer"; end) describe("resolve()", function() local example; setup(function() example = json.decode([[{ "foo": ["bar", "baz"], "": 0, "a/b": 1, "c%d": 2, "e^f": 3, "g|h": 4, "i\\j": 5, "k\"l": 6, " ": 7, "m~n": 8 }]]) end) it("works", function() assert.is_nil(jp.resolve("string", "/string")) assert.same(example, jp.resolve(example, "")); assert.same({ "bar", "baz" }, jp.resolve(example, "/foo")); assert.same("bar", jp.resolve(example, "/foo/0")); assert.same(nil, jp.resolve(example, "/foo/-")); assert.same(0, jp.resolve(example, "/")); assert.same(1, jp.resolve(example, "/a~1b")); assert.same(2, jp.resolve(example, "/c%d")); assert.same(3, jp.resolve(example, "/e^f")); assert.same(4, jp.resolve(example, "/g|h")); assert.same(5, jp.resolve(example, "/i\\j")); assert.same(6, jp.resolve(example, "/k\"l")); assert.same(7, jp.resolve(example, "/ ")); assert.same(8, jp.resolve(example, "/m~0n")); end) end) end)