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

Generate doxygen docs for FC #741

Closed
abitmore opened this issue Mar 19, 2018 · 5 comments
Closed

Generate doxygen docs for FC #741

abitmore opened this issue Mar 19, 2018 · 5 comments
Assignees
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) documentation

Comments

@abitmore
Copy link
Member

We now have a Doxyfile in FC (done with bitshares/bitshares-fc#12), so we can generate docs. But there are still some questions:

  • Where should we put/link the FC doxygen document?
  • Is it possible to have the FC doc included when generating docs for BitShare-Core? And, is it good to do so?
@cedar-book
Copy link

@abitmore, New link was added here for the BitShares-fc: Doxygen Documentation website.

@abitmore
Copy link
Member Author

@oxarbitrage I guess need to update the doxygen files here? It's generated in February, lately we've added some new code to FC.

@oxarbitrage
Copy link
Member

updated http://open-explorer.io/doxygen/fc/

probably not the best place to host it, that was a test but will work for now.

@cedar-book
Copy link

@oxarbitrage, if you want to replace by another link path, just let me know. I'll update it. :)

@abitmore abitmore added this to the 3.3.0 - Feature Release milestone Jul 17, 2019
@abitmore abitmore added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) and removed question labels Jul 17, 2019
@oxarbitrage
Copy link
Member

Closed by #1851 where FC documentation is added to bitshares-core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) documentation
Projects
None yet
Development

No branches or pull requests

3 participants