Make Patch `state` field similar to Issue

Since they are similar objects, they should have similar structure.
This also makes it easier to add state metadata like for issues.
This commit is contained in:
Alexis Sellier 2023-03-13 13:55:12 +01:00
parent f7aac06a8f
commit 7266729924
No known key found for this signature in database
2 changed files with 4 additions and 4 deletions

View File

@ -1351,7 +1351,7 @@ mod routes {
},
"title": "A new `hello word`",
"description": "change `hello world` in README to something else",
"state": "proposed",
"state": { "status": "proposed" },
"target": "delegates",
"tags": [],
"revisions": [
@ -1382,7 +1382,7 @@ mod routes {
},
"title": "A new `hello word`",
"description": "change `hello world` in README to something else",
"state": "proposed",
"state": { "status": "proposed" },
"target": "delegates",
"tags": [],
"revisions": [
@ -1452,7 +1452,7 @@ mod routes {
},
"title": "Update README",
"description": "Do some changes to README",
"state": "proposed",
"state": { "status": "proposed" },
"target": "delegates",
"tags": [],
"revisions": [

View File

@ -399,7 +399,7 @@ impl Revision {
}
#[derive(Debug, Clone, Copy, Default, PartialEq, Eq, PartialOrd, Ord, Serialize, Deserialize)]
#[serde(rename_all = "camelCase")]
#[serde(rename_all = "camelCase", tag = "status")]
pub enum State {
#[default]
Proposed,