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

Add documentation for dev-forget-channel command too #6923

Closed
4 tasks
ShahanaFarooqui opened this issue Dec 8, 2023 · 6 comments · Fixed by #7041
Closed
4 tasks

Add documentation for dev-forget-channel command too #6923

ShahanaFarooqui opened this issue Dec 8, 2023 · 6 comments · Fixed by #7041
Assignees
Labels

Comments

@ShahanaFarooqui
Copy link
Collaborator

ShahanaFarooqui commented Dec 8, 2023

Currently, documentation for dev-forget-channel command is missing and will be helpful to add for easier user reference.

For the RPC command:

  • Add *.request.json in doc/schemas with RPC request inputs types, descriptions, etc.
  • Add *.schema.json in doc/schemas, detailing RPC response, fields descriptions, defaults, etc.
  • Include lightning-*.7.md file in doc, where RETURN VALUE should be generated dynamically using tools/fromschema.py script
  • make doc-all should auto generate lightning-*.7 from lightning-*.7.md
@bitkarrot
Copy link
Contributor

@ecurrencyhodler told me about this issue on stakwork. I am interested. @ShahanaFarooqui

@cdecker
Copy link
Member

cdecker commented Jan 15, 2024

I wonder if we should really be documenting these. We decided against including the dev- commands in the help output because they are, well, intended for developers. In addition they are commands that are mostly used to manipulate the internals during tests, and do not have a solid interface, i.e., we'd continually be breaking semantic versioning, or we'd have to start building tiny ad-hoc commands to test things in the tests.

These then would also be documented, exposed to users, and users that do not know the intricacies of the dev- commands may end up trying them out and destroying their node.

@rustyrussell what do you think?

@ShahanaFarooqui
Copy link
Collaborator Author

Adding some context from where it started:
Reference issue: Ride-The-Lightning/RTL#1280

A user wanted to forget 3 channels and was unable to execute the command due to missing short_channel_id. Finally, @rustyrussell confirmed that channel_id can also be used. Then he asked to open an issue to add dev documentation with details so that advanced users can refer to the documentation if needed.

However, we can show these commands under advanced category with extra warning, if that helps.

@bitkarrot
Copy link
Contributor

I was just about to ask @ShahanaFarooqui to clarify the task.

Either way I am totally ok what your decision is, to document or not to document. I just got my environment updated and probably won't have time to work on it immediately, so no worries if you guys want to cancel this task. We can also just make a framework and leave it with placeholders if you want.

@ShahanaFarooqui ShahanaFarooqui changed the title Add documentation for all dev commands too Add documentation for dev-forget-channel command too Feb 2, 2024
@ShahanaFarooqui ShahanaFarooqui removed this from the v24.02 milestone Feb 2, 2024
@ShahanaFarooqui
Copy link
Collaborator Author

@cdecker After confirming with @rustyrussell, we decided to only add documentation for dev-forget-channel. So updated the issue accordingly.

@bitkarrot
Copy link
Contributor

@ShahanaFarooqui ok I'll take a look this weekend and will send questions here if not clear. thanks for the update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants