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

Enhancement: Introduce Code Formatting and Development Environment Configuration #462

Conversation

Andronovo-bit
Copy link
Collaborator

@Andronovo-bit Andronovo-bit commented Jan 17, 2024

Description

This pull request, identified as [HUP-784], introduces essential changes related to the project's code formatting and development environment configuration. The following key changes have been made:

  • Created configuration files for code editors (.editorconfig and settings.json for Visual Studio Code) and a vsconfig file for Visual Studio to ensure consistent development practices.
  • Added common components and settings that are recommended for a streamlined development experience.

Related Issues

N/A

Checklist

Before submitting this pull request, the following checks have been completed:

  • Code follows the project's coding standards and conventions.
  • Code has been reviewed for logic errors and bugs.
  • Code has been tested in the intended Unity environment.
  • Automated tests (if applicable) have been added and pass successfully. (Note: Please add automated tests if needed.)
  • Documentation has been updated (if changes impact existing documentation).
  • Dependencies have been resolved and updated (if any).

Screenshots / Visuals (if applicable)

N/A

Additional Context (if necessary)

N/A

Reviewer Guidance

Reviewers are encouraged to focus on the following aspects during the code review:

  • Code readability and adherence to coding standards.
  • Functional correctness and expected behavior.
  • Proper handling of edge cases and error scenarios.
  • Potential impact on performance or memory usage.
  • Thoroughness of testing coverage.

Reviewer Checklist

Reviewers should pay attention to the following:

  • Code readability and adherence to coding standards.
  • Functional correctness and expected behavior.
  • Proper handling of edge cases and error scenarios.
  • Impact on performance or memory usage.
  • Testing coverage and thoroughness.

Test Plan

To test the changes made in this pull request, follow these steps:

  1. Verify that the newly created configuration files (editorconfig, settings.json, and vsconfig) are correctly placed in the project.
  2. Ensure that the formatting and settings defined in these files align with the project's coding standards.
  3. If automated tests were added, execute them to confirm their successful execution and expected outcomes.

Deployment Notes

N/A

Assignees

@alihan98ersoy

… vsconfig configs.

-Created editorconfig file and added fundamental settings.
-Created vsconfig file and added common components for visual studio.
-Created extensions.json for common extension recommendation.
-Created settings.json file added common settings for tho using vscode.
…oject.

-Fixed space, whitespace, indention and tabs, mean formatted all these file.
-Deleted unused usings

Notes: There are many file in this commit but just a little changes in files.
…project.

-Fixed space, whitespace, indention and tabs, mean formatted all these file.
-Deleted unused usings

Notes: There are many file in this commit but just a little changes in files.
…ect.

-Fixed space, whitespace, indention and tabs, mean formatted all these file.
-Deleted unused usings
@alihan98ersoy alihan98ersoy merged commit ce0557f into EvilMindDevs:master Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants