Server

[Dylanflini]

Summary

The issue

Diagnosis of the issue (bugs only)

Solution implemented

Considerations of the solution

References

Self review

• [ ] I have reviewed my PR changes and left comments/questions when necessary
• [ ] I have added a screenshot for the applied changes.
• [ ] I have followed the style guidelines of this project.
• [ ] I have added and ran the tests locally.
• [ ] I have ran the test coverage reports locally.
• [ ] I have made corresponding changes to the documentation (README and API).
• [ ] I have added the abstraction layers needed to separate responsibilities.

Impact of these changes

This changes through Component impacts:

• Component1
• Component2
• Component3

Evidences of expected changes

Add evidences here about each impact generated by your changes

Type of change

• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] Hot fix (fixes an issue in master branch)
• [ ] Docs (Documentation only changes)
• [ ] Style (Changes that do not affect the meaning of the code, formatting, missing semi-colons, etc)
• [ ] Refactor (Changes that neither fixes a bug or adds a feature)
• [ ] Performance (Changes that improve performance)
• [ ] Chore (Changes to the build process or auxiliary tools and libraries)

Squash and merge

We are following Angular commit messages guidelines

<type>(<scope>): <Jira-Issue subject>
<BLANK LINE>
<optional body>
<BLANK LINE>
<optional footer>

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Make sure you squash and merge your feature/bugfix branches into develop/release/hotfix branches using the suggested format.

Some examples.

feat: DP-1234 Edit assessment information
Frontend changes for editing an assessment:
- improve assign modal to receive an existing assessment
- integrate the reasign end point.
- couple of warnings removed
BREAKING CHANGE: the assign modal now receives 3 required parameters

More examples here