2021-11-10 21:04:01 +00:00
|
|
|
### What does the PR do
|
|
|
|
|
|
|
|
|
|
<!-- Fill in the relevant information below to help us evaluate your proposed changes. -->
|
|
|
|
|
|
|
|
|
|
### Affected areas
|
|
|
|
|
|
|
|
|
|
<!-- List the affected areas (e.g wallet, browser, etc..) -->
|
|
|
|
|
|
2024-07-11 11:27:05 +00:00
|
|
|
### Architecture compliance
|
2022-09-21 15:58:43 +00:00
|
|
|
|
2024-07-11 11:27:05 +00:00
|
|
|
- [ ] I am familiar with the application architecture and agreed good practices.
|
|
|
|
|
My PR is consistent with this document: [Architecture guidelines](../architecture-guide.md)
|
2022-09-21 15:58:43 +00:00
|
|
|
|
2022-07-07 12:55:05 +00:00
|
|
|
### Screenshot of functionality (including design for comparison)
|
|
|
|
|
|
|
|
|
|
- [ ] I've checked the design and this PR matches it
|
2021-11-10 21:04:01 +00:00
|
|
|
|
|
|
|
|
<!-- screenshot (or gif/video) that demonstrates the functionality, specially important if it's a bug fix. -->
|
|
|
|
|
|
2024-07-03 16:00:31 +00:00
|
|
|
<!-- Uncomment this section for status-go upgrade/dogfooding pull requests
|
|
|
|
|
|
|
|
|
|
### Impact on end user
|
|
|
|
|
|
|
|
|
|
What is the impact of these changes on the end user (before/after behaviour)
|
|
|
|
|
|
|
|
|
|
### How to test
|
|
|
|
|
|
|
|
|
|
- How should one proceed with testing this PR.
|
|
|
|
|
- What kind of user flows should be checked?
|
|
|
|
|
|
|
|
|
|
### Risk
|
|
|
|
|
|
|
|
|
|
Described potential risks and worst case scenarios.
|
|
|
|
|
|
|
|
|
|
Tick **one**:
|
|
|
|
|
- [ ] Low risk: 2 devs MUST perform testing as specified above and attach their results as comments to this PR **before** merging.
|
|
|
|
|
- [ ] High risk: QA team MUST perform additional testing in the specified affected areas **before** merging.
|
|
|
|
|
|
|
|
|
|
-->
|
