Opened at 2009-01-03T01:48:52Z
Last modified at 2020-07-14T15:02:17Z
#567 assigned enhancement
add version info to t=JSON output data — at Version 2
| Reported by: | warner | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | soon |
| Component: | code-frontend-web | Version: | n/a |
| Keywords: | version json docs easy forward-compatibility | Cc: | freestorm77@… |
| Launchpad Bug: |
Description (last modified by freestorm)
Change History (3)
comment:1 Changed at 2010-03-25T01:11:36Z by davidsarah
- Keywords version json docs easy forward-compatibility added
comment:2 Changed at 2010-05-30T19:46:43Z by freestorm
- Description modified (diff)
Changed at 2010-05-30T19:48:36Z by freestorm
Note: See
TracTickets for help on using
tickets.
It will probably make life easier in the future if we add a version number to the JSON output from operations like deep-stats, deep-manifest, and deep-check.
A related piece would be to tell developers that they should tolerate the presence or absence of each field.
On the other hand, the only customers of the t=JSON are:
1) The Tahoe CLI
2) Tools written to use the webapi functions
I'm ok with requiring that you use e.g. a 1.3.0 CLI with a 1.3.x backend instead of a 1.4.x backend, and developers have to play catchup all the time anyways.
So I'm not sure how much energy I want to put into this.