BC-6660 - Add is editable to response #4971
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dyedwiper
reviewed
Apr 30, 2024
apps/server/src/modules/user/legacy/service/users-admin.service.ts
Outdated
Show resolved
Hide resolved
dyedwiper
approved these changes
May 6, 2024
|
|
Requirements changed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Both teachers and admins have the option to open the edit mode / pen of the data record in "Management > Students".
This should be locked in "Management > Students", just like it is should be locked in "Management > teachers".
It should not be possible to change the data in the TSC, as the data comes from the TSP.
Links to Tickets or other pull requests
JIRA : https://ticketsystem.dbildungscloud.de/browse/BC-6660
Changes
Datasecurity
Deployment
New Repos, NPM pakages or vendor scripts
Approval for review
generate-client:serverwas executed in vue frontend and changes were tested and put in a PR with the same branch name.