Remove forced lf in .editorconfig

[MattKotsenas]

#215 added the new .gitattributes from .NET, which does git normalization and lets IDEs use the OS default. This avoids a bunch of eol churn because some tools respect .editorconfig and some do not. However, I forgot to remove the forced lf in .editorconfig which meant we still got eol churn caused by tools that did respect .editorconfig.

This change removes eol settings from .editorconfig and should (finally) fix eol churn.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in the .editorconfig file include updates to formatting and coding conventions for C# and VB files. Key modifications involve setting indent_size and tab_width to 4, changing end_of_line to lf, and enabling insert_final_newline. Diagnostic severity levels for various C# coding conventions have been adjusted, and new naming style rules have been introduced. Additionally, the handling of TODO comments has been refined with specific severity levels assigned to related diagnostic rules.

Changes

File	Change Summary
.editorconfig	Updated formatting and coding conventions for C# and VB files, including indentation, naming styles, and diagnostic severity levels.

Possibly related PRs

• Add *.props and *.targets to XML section of .editorconfig template #240: The changes in this PR also involve modifications to the .editorconfig file, specifically regarding indentation settings and naming conventions for C# files, which directly relate to the updates made in the main PR.

Suggested labels

.NET, dependencies

Suggested reviewers

• rjmurillo

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 200fbaf and a09b310.

📒 Files selected for processing (1)

• .editorconfig (0 hunks)

💤 Files with no reviewable changes (1)

• .editorconfig

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[qlty-cloud-legacy]

Code Climate has analyzed commit a09b310 and detected 0 issues on this pull request.

View more on Code Climate.