Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API documentation #780

Closed
5 of 8 tasks
abitmore opened this issue Mar 24, 2018 · 6 comments
Closed
5 of 8 tasks

API documentation #780

abitmore opened this issue Mar 24, 2018 · 6 comments
Assignees
Labels
1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2c Ready for Development Status indicating the Requirements are sufficent to begin designing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) api documentation

Comments

@abitmore
Copy link
Member

abitmore commented Mar 24, 2018

See api.hpp, get_fill_order_history and some other API's don't have in-code documentation, we need to complete them, like get_account_history.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Design / Develop Solution
    • Issue estimation: 5 hours (20 AUG: revised to 5 hours from 2 hours)
    • Issue assigned to @cogutvalera
    • Remitted: Week 39
  • Perform QA/Testing
  • Update Documentation
@ryanRfox ryanRfox added 1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2c Ready for Development Status indicating the Requirements are sufficent to begin designing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) labels May 24, 2018
@cogutvalera
Copy link
Member

I want to claim this issue

cogutvalera pushed a commit to cogutvalera/bitshares-core that referenced this issue Jul 25, 2018
cogutvalera pushed a commit to cogutvalera/bitshares-core that referenced this issue Jul 25, 2018
@ryanRfox
Copy link
Contributor

Updating estimation to 2 hours.

@cogutvalera
Copy link
Member

Thanks !

cogutvalera pushed a commit to cogutvalera/bitshares-core that referenced this issue Jul 31, 2018
@ryanRfox
Copy link
Contributor

Revised estimate to 5 hours from 2 hours.

abitmore added a commit that referenced this issue Oct 6, 2018
@cogutvalera
Copy link
Member

Done by #1174
We can close this issue.

@abitmore abitmore closed this as completed Oct 6, 2018
@cogutvalera
Copy link
Member

Thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1c Task Task for team member to perform. Description may contain a Task List and reference child Sub-Tasks 2c Ready for Development Status indicating the Requirements are sufficent to begin designing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) api documentation
Projects
None yet
Development

No branches or pull requests

3 participants