You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull Requests to SSW.Rules often fail due to linter errors. To mitigate this in the future I suggest adding the following files into the .vscode folder:
Settings.json – overrides settings for the current workspace (In this case it would set Prettier as the format on save option)
Extensions.json – Recommended plugins to download when working with the current workspace. (see below for the list of plugins that we will add initially)
.editorconfig (in the root directory) - Recommended to help maintain consistent coding styles across various editors and IDEs EditorConfig
Update Readme.md file
In the ”developer” section add a step to install the recommended plugins
In the “Definition of Done” section add a dotpoint to ensure people are using the recommended plugins
Figure: Adding the extensions.json file prompts the user to add the recommended VS Code plugins (whenever someone opens up the project in VS Code)
Formatting plugins
The below plugins will enforce the ESLint rules by overwriting certain VS Code settings ensuring “FormatOnSave” is turned on and the correct formatter is selected.
dbaeumer.vscode-eslint - ESLint (ESLint - Visual Studio Marketplace)
EditorConfig.EditorConfig - EditorConfig for VS Code (EditorConfig for VS Code - Visual Studio Marketplace)
The below plugin will ensure everyone is using the same emojis when committing and will keep commit messages short and to the point with a warning being displayed when over 50 characters.
vtrois.gitmoji-vscode – Gitmoji (Gitmoji - Visual Studio Marketplace)
cc @adamcogan , @bradystroud and @pierssinclairssw
To Myself,
As per my conversation with @adamcogan , @bradystroud and @pierssinclairssw,
Pull Requests to SSW.Rules often fail due to linter errors. To mitigate this in the future I suggest adding the following files into the .vscode folder:
Figure: Adding the extensions.json file prompts the user to add the recommended VS Code plugins (whenever someone opens up the project in VS Code)
Formatting plugins
The below plugins will enforce the ESLint rules by overwriting certain VS Code settings ensuring “FormatOnSave” is turned on and the correct formatter is selected.
GitLens plugin
The below plugin will ensure everyone is benefitting from using source control as per rule: Do you know the benefits of using source control?
Gitmoji plugin
The below plugin will ensure everyone is using the same emojis when committing and will keep commit messages short and to the point with a warning being displayed when over 50 characters.
AB#64835
The text was updated successfully, but these errors were encountered: