Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Issues
  • #350

Closed
Open
Created Jan 31, 2020 by Mark Brooker@walkjiveflyMaintainer0 of 5 tasks completed0/5 tasks

Enhancement request: allow use of "*" for (current) chain height in nftoken list and nftproto list

User Story/Motivation/Problem

Chain height is an optional parameter that defaults to current chain height, but to use the count and skip paging values it must be specified. It's inconvenient to have to get the current height before issuing the query. A convenience for the user would be able to specify "*" for current chain height.

Also, it would be nice not to have to quote the asterisk when used as a placeholder for protocol name or owner address.

Requirements

(If you can - please define the requirements, if not - skip it).

Tasks

  • (To be defined by devs)
  • Unit-tests
  • Refactor
  • Code Review
  • QA

Definition of done/Acceptance criteria

  • Ready for production after QA check.

How to demo

(To be defined by devs).

Link/refs/notes/images

/cc @artem

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking