Skip to content

🚧Process all warnings in code base #120

@CalvinWilkinson

Description

@CalvinWilkinson

Complete The Item Below

  • I have updated the title without removing the 🚧 emoji.

Description

Go through all of the warnings generated by the analyzers as well as the build results and process them.

This is a cleanup of the entire code base.

Acceptance Criteria

  • Update all .editorconfig files.

    Warning Do this before processing any warnings

  • All analyzer warnings processed
  • All build warnings process

    Note These are the warnings that you can see in the Build tab in JetBrains Rider

  • Go through all constructors and make all of the injected param code docs the same.
  • Add code docs to all unit test files with missing code docs

ToDo Items

  • Change type labels added to this issue. Refer to the Change Type Labels section below.
  • Priority label added to this issue. Refer to the Priority Type Labels section below.
  • Issue linked to the correct project (if applicable).
  • Issue linked to the correct milestone (if applicable).
  • Draft pull request created and linked to this issue (only required with code changes).

Issue Dependencies

No response

Related Work

No response

Additional Information:

Change Type Labels

Change Type Label
Bug Fixes 🐛bug
Breaking Changes 🧨breaking changes
New Feature ✨new feature
Workflow Changes workflow
Code Doc Changes 🗒️documentation/code
Product Doc Changes 📝documentation/product

Priority Type Labels

Priority Type Label
Low Priority low priority
Medium Priority medium priority
High Priority high priority

Code of Conduct

  • I agree to follow this project's Code of Conduct.

Metadata

Metadata

Labels

breaking-changesFeature/changes contains breaking changesmedium-priorityMedium PrioritypreviewDone while in preview

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions