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.

Sign up for GitHub

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

Jump to bottom

VSCode QOL Improvements #966

Merged
merged 1 commit into from
Nov 25, 2024
Merged

VSCode QOL Improvements #966

merged 1 commit into from
Nov 25, 2024

Conversation

Piras314
Copy link
Member

@Piras314 Piras314 commented Nov 25, 2024 •
edited by coderabbitai bot
Loading

About the PR

Add Tools and Release VSCode launch configurations, and add gitlens, robust LSP, and github PRs to the extension recommendations

Why / Balance

I hate having to type the commands in when I want to test release or map/run tools

Technical details

Media

Tested all configs, here's a screenshot of Release to show it's working:

image

Requirements

Breaking changes

Changelog

no CL no fun

Summary by CodeRabbit

  • New Features

    • Added three recommended extensions for improved development experience.
    • Introduced new debugging configurations for both tools and release builds.
    • Added new build tasks for .NET projects to streamline the build process.

  • Enhancements

    • Expanded debugging capabilities with compound configurations for server and client setups.

@Piras314
Add Tools and Release VSCode launch configurations, and add gitlens, …
8962d30 
…robust LSP, and github PRs to the extension recommendations
@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 25, 2024 •
edited
Loading

Caution

Review failed

The pull request is closed.

Walkthrough

OwO! The changes in this pull request add new extension recommendations and enhance the debugging setup in Visual Studio Code. Three extensions are now recommended in the .vscode/extensions.json file, and the .vscode/launch.json file sees the addition of multiple configurations for tools and release builds, along with compound configurations. Lastly, the .vscode/tasks.json file introduces two new build tasks for .NET projects, expanding the build options available. Pounces on you with excitement!

Changes

File Change Summary
.vscode/extensions.json Added recommendations for extensions: "ertanic.robust-lsp", "GitHub.vscode-pull-request-github", "eamodio.gitlens"
.vscode/launch.json Added configurations: "Client - Tools", "Client (Compatibility renderer) - Tools", "Server - Tools", "Client - Release", "Client (Compatibility renderer) - Release", "Server - Release", "Server/Client - Tools", "Server/Client - Release"
.vscode/tasks.json Added tasks: "build - Tools" and "build - Release"

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant VSCode
    participant Extensions
    participant Tasks
    participant Launch

    User->>VSCode: Open project
    VSCode->>Extensions: Load recommended extensions
    Extensions-->>VSCode: Extensions loaded
    VSCode->>Launch: Load launch configurations
    Launch-->>VSCode: Configurations loaded
    VSCode->>Tasks: Load tasks
    Tasks-->>VSCode: Tasks loaded
    VSCode-->>User: Ready to debug and build! UwU
Loading

Poem

In VSCode's realm where coders play,
New tools and tasks come out to sway,
Extensions gleam, oh what a sight!
Debugging dreams take glorious flight!
Pounces on the code, oh what a thrill,
With every change, we code and chill! ✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the No C# label Nov 25, 2024
@Piras314 Piras314 merged commit 7fb121a into Goob-Station:master Nov 25, 2024
9 checks passed
@Piras314 Piras314 deleted the vscode-improvements branch November 25, 2024 20:00
Aviu00 pushed a commit to Aviu00/Goob-Station that referenced this pull request Nov 27, 2024
@Piras314 @Aviu00
VSCode QOL Improvements (Goob-Station#966)
47b8864 
Add Tools and Release VSCode launch configurations, and add gitlens, robust LSP, and github PRs to the extension recommendations
@Piras314 Piras314 mentioned this pull request Dec 16, 2024
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
No C#
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Piras314