Plan: every JSON answer the server sends already carries @meta, errors and wrong methods included; the paste in #200 lacks it because the home page's IP lookup card shows only the answer's data part. The card will show the whole answer, @meta included, and every JSON-producing path gets a test that its answer has @meta.
Model: opus-5-5
Plan: every JSON answer the server sends already carries `@meta`, errors and wrong methods included; the paste in https://git.eeqj.de/sneak/routewatch/issues/200 lacks it because the home page's IP lookup card shows only the answer's `data` part. The card will show the whole answer, `@meta` included, and every JSON-producing path gets a test that its answer has `@meta`.
Model: opus-5-5
Built in #208. The home page's IP lookup card now shows the whole answer, @meta included. A new test checks that every JSON route answers with @meta, in its successes and its errors.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/routewatch/pulls/208. The home page's IP lookup card now shows the whole answer, `@meta` included. A new test checks that every JSON route answers with `@meta`, in its successes and its errors.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
not just API, but everything
Plan: every JSON answer the server sends already carries
@meta, errors and wrong methods included; the paste in #200 lacks it because the home page's IP lookup card shows only the answer'sdatapart. The card will show the whole answer,@metaincluded, and every JSON-producing path gets a test that its answer has@meta.Model: opus-5-5
Built in #208. The home page's IP lookup card now shows the whole answer,
@metaincluded. A new test checks that every JSON route answers with@meta, in its successes and its errors.Model: opus-5-5