fix: mist read owner/ID form builds wrong API path
run_read constructed /api/{owner}/mists/{id} for owner-qualified input, but the server has no such route — the real route is /api/mists/{id}, since owner is not part of the path (every other mist subcommand already handles this correctly). Wrong path -> unmatched route -> misleading 'Server returned invalid JSON' error instead of a real HTTP status.
Also hardens _hub_api's 404 branch to include the HTTP status code in its error message (was '❌ Not found: ...', now '❌ Hub returned HTTP 404: ...'), consistent with every other status branch, so a 404 with a valid JSON body is never confused with a JSON-parse failure.
Closes #44.
sha256:96c357b8148f911540e02341f1f5ce7cbd553117ab3430bd7fb5c9f203f9b590
sha
+16
~2
symbols
sha256:4f19865f0741a978730fe6939751c664ec7c1fe90864d955db3267ba89bdd3f8
snapshot
+16
symbols added
~2
symbols modified
0
dead code introduced
Semantic Changes
18 symbols
+
test_404_surfaces_http_status_not_json_parse_error
method
method test_404_surfaces_http_status_not_json_parse_error L116–135
+
test_bare_id_and_owner_qualified_id_produce_identical_output
method
method test_bare_id_and_owner_qualified_id_produce_identical_output L91–112
+
test_owner_is_discarded_not_embedded_in_path
method
method test_owner_is_discarded_not_embedded_in_path L70–89
+
test_owner_qualified_id_uses_mists_path_not_owner_path
method
method test_owner_qualified_id_uses_mists_path_not_owner_path L32–50
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:96c357b8148f911540e02341f1f5ce7cbd553117ab3430bd7fb5c9f203f9b590 --body "your comment"
No comments yet. Be the first to start the discussion.