Merge pull request #177 from eosrio/fix/hot-first-response-schema

fix(api): declare hot_first in response schema so it isn't stripped

Author: igorls

src/api/helpers/functions.ts

@@ -781,6 +781,7 @@ export function extendResponseSchema(responseProps: any) {
         query_time_ms: {type: "number"},
         cached: {type: "boolean"},
         hot_only: {type: "boolean"},
+        hot_first: {type: "boolean"},
         lib: {type: "number"},
         last_indexed_block: {type: "number"},
         last_indexed_block_time: {type: "string"},

tests/unit/api-helpers.test.ts

@@ -152,6 +152,10 @@ describe('extendResponseSchema', () => {
         expect(props.cached).toBeDefined();
         expect(props.lib).toBeDefined();
         expect(props.total).toBeDefined();
+        // hot_only / hot_first must be declared or fast-json-stringify silently strips them
+        // from the response even when the handler sets them.
+        expect(props.hot_only).toBeDefined();
+        expect(props.hot_first).toBeDefined();
         expect(props.actions).toEqual({ type: 'array' });
     });
 });