According to decision 2024-11-18_1, add regular user type to all createHeaders() invocations in the tests (without parameter)
🔧 Why We Need This
Now only the admin user is stated explicitly. In one of the PRs also custom user is introduced. Explicit stating of regular user will help new contributors to comprehend the tests.
Additionally, if we decide to replace the regular user with a custom user in the future, it will be easier to do so.
🚀 Proposed Solution
It would be best to wait for merging the PR #128 introducing new enum for user type
✅ Issue reporting checklist
[x] I created a descriptive title for this issue
[x] I checked that it hasn't been reported yet
[x] I assigned the issue or added help-wanted label
✏️ Description
According to decision 2024-11-18_1, add regular user type to all
createHeaders()invocations in the tests (without parameter)🔧 Why We Need This
Now only the admin user is stated explicitly. In one of the PRs also custom user is introduced. Explicit stating of regular user will help new contributors to comprehend the tests. Additionally, if we decide to replace the regular user with a custom user in the future, it will be easier to do so.
🚀 Proposed Solution
It would be best to wait for merging the PR #128 introducing new enum for user type
✅ Issue reporting checklist
help-wantedlabel