Output blockchain APIs in a format that can be used for documentation #131
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#131
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
lbry.tech will be used to showcase the API signatures for the daemon, blockchain, and any other key components.
@lyoshenka did this get discussed on blockchain weekly?
Waiting on #44
Is this a duplicate of #143 ?
yes. ill close the other one.
reference #1276 from protocol
Also, see https://github.com/lbryio/lbry.tech/issues/42
and https://github.com/lbryio/lbry/blob/master/scripts/generate_json_api.py
I'm starting on this now and planning to pursue the jrgen plan.
@BrannonKing re: jrgen... if you'd like, take a look at this script I wrote for lbry-js; it's pretty barebones but generates a jrgen compatible schema file dynamically from the existing lbrycrd 'help' command.
@rynomad , thanks for posting that script. Unfortunately, my Python script was generally completed before I got this message yesterday. Hence, I think I'll proceed with my script.
I was unable to run your script. I'm not sure I followed your instructions correctly.
npm --version
reports 3.5.2. Do I need some other version? (There was nosetup
command on mine.)Ah, my bad, I had local changes days ago I had forgotten to push, should be good to go; also i fixed the readme; it's supposed to say
npm run setup