Details

    Description

      It is found that the field tokens used to interact with users in CLI or HTTP API requests have a relatively large overlap. This issue is hoped that a unified field output goal can be achieved through the field definition scheme, and the same attribute has a unified attribute definition and interpretation, which reduces the user's learning and use cost To maintain the consistency of interface interaction

      Because CLI and HTTP API are not a complete closed loop, and there are still compatibility issues, the existing ones are defined first, and then the new field definitions and interfaces will be gradually standardized. When appropriate, we will update the outdated interfaces.

      It should be noted that after the version is released, the existing definition fields in scheme cannot be modified, only new fields can be added

      Attachments

        Activity

          People

            gosonzhang Guocheng Zhang
            gosonzhang Guocheng Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h 20m
                1h 20m