USER STORY: Filtering based on contract metadata
As a developer user, I want to filter on contract metadata fields, so that I can use only the filtered data in my application.
Refer to TZIP-16: https://gitlab.com/tzip/tzip/-/blob/master/proposals/tzip-16/tzip-16.md and #230 (closed) and blocked by #262 (closed)
Example:
{ "version": "foo.1.4.2", "license": "ISC", "authors": [ "Seb Mondet <seb@mondet.org>" ], "interfaces": [ "TZIP-12" ], "views": [ // ... see below ... ] // ... potential extensions ...}
Acceptance criteria:
- When fetching smart contract account, user is able to filter on the following fields:
- name
- description
- version
- license
- name
- details
- authors
- source
- location
- tools
- interfaces
- errors - list or error or view entities, see below
{ "error": {"int": "42"},
"expansion": { "string": "You did something wrong"},
"languages": ["en"] },
{ "view": "translateStringError" }
- Supported cases:
- Storage types:
- tezos-storage:self
- with/without sha256 hash
- tezos-storage: refers to the other smart contract for the current network
- with/without sha256 hash
- tezos-storage:self
- Storage types:
SPLIT INTO A SEPARATE TICKET OR WAIT ON CACHING: http/https and ipfs items may not be loaded - Storage types: - tezos-storage: http/https - with or without sha256 - tezos-storage: ipfs - with or without sha256 - https://github.com/ipfs/in-web-browsers/blob/master/ADDRESSING.md#addressing-with-native-url - https://tezosguides.com/ipfs/
Edited by Alireza Haghshenas