fix: separate out rosetta request/response schema files from entity files

Several schema files referenced entity files in the docs/api/rosetta
directory.  They entity files have all been moved to docs/entities/rosetta
and references updated.

Author: asimm241

docker-compose.dev.postgres.yml

@@ -10,7 +10,7 @@ services:
       POSTGRES_DB: stacks_blockchain_api
       POSTGRES_PORT: 5432
     volumes:
-      - database-data:/var/lib/postgresql/data/ # persist data even if container shuts down
+      - ./psql-data:/var/lib/postgresql/data/
 
 volumes:
   database-data:

docs/api/rosetta/rosetta-account-balance-request.schema.json

@@ -13,8 +13,7 @@
       "$ref": "./../../entities/rosetta/rosetta-account.schema.json"
     },
     "block_identifier": {
-      "$ref": "./../../entities/rosetta/rosetta-block-identifier.schema.json"
+      "$ref": "./../../entities/rosetta/rosetta-partial-block-identifier.schema.json"
     }
-  },
-  "additionalProperties": true
+  }
 }

docs/api/rosetta/rosetta-account-balance.example.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema",
-  "$id": "rosetta-account",
+  "$id": "rosetta-account-response",
   "type": "object",
   "title": "RosettaAccountBalanceResponse",
   "description": "An AccountBalanceResponse is returned on the /account/balance endpoint. If an account has a balance for each AccountIdentifier describing it (ex: an ERC-20 token balance on a few smart contracts), an account balance request must be made with each AccountIdentifier.",

docs/api/rosetta/rosetta-account-response.schema.json

@@ -3,14 +3,14 @@
   "$id": "rosetta-block-request",
   "type": "object",
   "title": "RosettaBlockRequest",
-  "description": "A MempoolTransactionRequest is utilized to retrieve a transaction from the mempool.",
+  "description": "A BlockRequest is utilized to make a block request on the /block endpoint.",
   "required": ["network_identifier", "block_identifier"],
   "properties": {
     "network_identifier": {
       "$ref": "./../../entities/rosetta/rosetta-network-identifier.schema.json"
     },
     "block_identifier": {
-      "$ref": "./../../entities/rosetta/rosetta-block-identifier.schema.json"
+      "$ref": "./../../entities/rosetta/rosetta-partial-block-identifier.schema.json"
     }
   }
 }

docs/api/rosetta/rosetta-block-identifier.schema.json

@@ -7,13 +7,13 @@
   "required": [],
   "properties": {
     "block": {
-      "$ref": "./rosetta-block.schema.json"
+      "$ref": "./../../entities/rosetta/rosetta-block.schema.json"
     },
     "other_transactions": {
       "type": "array",
       "description": "Some blockchains may require additional transactions to be fetched that weren't returned in the block response (ex: block only returns transaction hashes). For blockchains with a lot of transactions in each block, this can be very useful as consumers can concurrently fetch all transactions returned.",
       "items": {
-        "$ref": "./rosetta-other-transaction-identifier.schema.json"
+        "$ref": "./../../entities/rosetta/rosetta-other-transaction-identifier.schema.json"
       }
     }
   }

docs/api/rosetta/rosetta-block-request.schema.json

@@ -13,7 +13,7 @@
       "$ref": "./../../entities/rosetta/rosetta-block-identifier.schema.json"
     },
     "transaction_identifier": {
-      "$ref": "./rosetta-transaction-identifier.schema.json"
+      "$ref": "./../../entities/rosetta/rosetta-transaction-identifier.schema.json"
     }
   }
 }

docs/api/rosetta/rosetta-block-response.schema.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema",
+  "$id": "rosetta-block-transaction-response",
+  "type": "object",
+  "title": "RosettaBlockTransactionResponse",
+  "description": "A BlockTransactionResponse contains information about a block transaction.",
+  "required": ["transaction"],
+  "properties": {
+    "transaction": {
+      "$ref": "./../../entities/rosetta/rosetta-transaction.schema.json"
+    }
+  }
+}

docs/api/rosetta/rosetta-block-transaction-request.schema.json

@@ -1,15 +1,16 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema",
   "type": "object",
-  "title": "RosettaMempoolTransactionRequest",
-  "description": "Get a transaction in the mempool by its Transaction Identifier. This is a separate request than fetching a block transaction (/block/transaction) because some blockchain nodes need to know that a transaction query is for something in the mempool instead of a transaction in a block. Transactions may not be fully parsable until they are in a block (ex: may not be possible to determine the fee to pay before a transaction is executed). On this endpoint, it is ok that returned transactions are only estimates of what may actually be included in a block.",
-  "required": ["network_identifier", "transaction_identifier"],
+  "title": "RosettaMempoolTransactionListRequest",
+  "description": "Get all Transaction Identifiers in the mempool",
+  "required": ["network_identifier"],
   "properties": {
     "network_identifier": {
-      "$ref": "./rosetta-network-identifier.schema.json"
+      "description": "The network_identifier specifies which network a particular object is associated with.",
+      "$ref": "./../../entities/rosetta/rosetta-network-identifier.schema.json"
     },
-    "transaction_identifier": {
-      "$ref": "./rosetta-transaction-identifier.schema.json"
+    "metadata": {
+      "type": "object"
     }
   }
 }