-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[docs][guides] Docs page for REPL #7484
Comments
Hey @kkemple! |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
Awesome! I believe it's merged now. |
Hey @kkemple. Feeling a lil embarassed to admit that I don't have a clue where to start. I found the list of REPL commands, but I am unable to understand the motivation for such a feature. Please help. |
@V1shvesh Original idea came from #6952 and it was implemented in #7484 . For the most part it is to allow examining internal state of Gatsby, without resorting to bunch of It might be useful during development/debugging of plugins, but it does require knowledge of Gatsby internals. Or using it can help people understand internals better (depending how you look at it). |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
@gatsbyjs/core is there anything we need to do to the Gatsby REPL to get it into shape for proper documentation? It is in the Gatsby CLI doc, but this issue is about filling in the top-level docs page. |
@marcysutton I'd love to give this a go! It might take me a week or two to get familiar with the commands and such to get some basic documentation together, but then we could go from there. It seems like I can just break up the commands into different pages, and show examples of how and why you would use each, as well as how this could be combined with the GraphQL explorer to be useful to folks. I can start with three or four commands and go from there. Thoughts? |
@n8finch sounds awesome! I think one page would be ideal, though. The work slated in #6896 would help to organize it–in the meantime we're using hard-coded tables of contents like on this doc: https://github.com/gatsbyjs/gatsby/blob/master/docs/docs/gatsby-image.md#in-this-doc |
@marcysutton perfect, I'll get to work on this! If the issue is quiet for a bit, don't worry, I'm still working... 🤓 |
A new
repl
command was added to Gatsby CLI but it is currently undocumented.The text was updated successfully, but these errors were encountered: