-
Notifications
You must be signed in to change notification settings - Fork 251
"Setting up a Development Environment": VS Code #360
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
Conversation
✅ Deploy Preview for nimble-elf-d9d491 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The VS Code-specific information is all neatly centralized in this article, while the same for IDEA is scattered everywhere in the Docs...
see:
getting-started/setting-up-a-development-environment/*.mdgetting-started/creating-a-project.md#importing-the-projectgetting-started/launching-the-game.mdide-tips-and-tricks.md
I don't think it has to be done in this PR, but I'm for creating getting-started/idea and getting-started/vscode with subpages for each topic.
I'm not saying all the docs have to be split, just the IDE-specific pages listed above.
develop/getting-started/setting-up-a-development-environment.md
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
|
I'd put "Setting Up a Development Environment" last in the sidebar: getting-started/:
- index.md # Introduction to Fabric and Modding
- creating-a-project.md
- project-structure.md
- setup-ide/:
- idea/:
- opening-the-project.md
- launching-the-game.md
- ...
- tips-and-tricks.md
- vscode/:
- ... |
its-miroma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's another possible solution for the headings, what do you think?
* upstream/main: Update rendering concepts page (FabricMC#362) "Setting up a Development Environment": VS Code (FabricMC#360) Running Game Tests In Github Actions (FabricMC#338) Items: Item Models (FabricMC#324) Call `.useBlockPrefixedTranslationKey()` (FabricMC#358) Clarify that `mod-id` placeholders must be customized (FabricMC#348) replace remaining mentions of tickDelta with tickProgress (FabricMC#361) Project location (FabricMC#326) improve the first items docs to state what's needed for item appearance, link fix (FabricMC#359)
* add page for setting up vscode, tips and re-arrange sidebar * address review comments * address review comments * address review comments * address review comments (cherry picked from commit 8d7d92f)
* add page for setting up vscode, tips and re-arrange sidebar * address review comments * address review comments * address review comments * address review comments (cherry picked from commit 8d7d92f)
* add page for setting up vscode, tips and re-arrange sidebar * address review comments * address review comments * address review comments * address review comments (cherry picked from commit 8d7d92f)
Still a hater, but surprisingly it works well enough.
This PR:
Should close #176. Given how few use Eclipse, it's not worth the effort.