-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: artist alley allow blocking specific users as well as disabling registration #216
Merged
Fenrikur
merged 16 commits into
main
from
198-Artist-Alley-allow-blocking-specific-users-as-well-as-disabling-registration
Sep 8, 2024
Merged
feat: artist alley allow blocking specific users as well as disabling registration #216
Fenrikur
merged 16 commits into
main
from
198-Artist-Alley-allow-blocking-specific-users-as-well-as-disabling-registration
Sep 8, 2024
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
… as disabling registration (#198) Added Record for storing user bans.
… as disabling registration (#198) Added api endpoint for changing the users status
… as disabling registration (#198) Added new buttons in the backoffice for banning a user feat(artistalley): Artist Alley allow blocking specific users as well as disabling registration (#198) Changes in the user's status will now be logged. BREAKING CHANGE: Added a new database table. DB update will be required
… as disabling registration (#198) Artist alley registrations can now be enabled and disabled via the backoffice or API. Disabling the artist alley registrations will result in a file .ArtistAlleyDisabled being created and deleted when the artist alley registrations are enabled again. Submitting a new table application is now only possible when the artist alley is enabled
Fixed a bug in the API, where the wrong object was serialized. Now when banning a user a reason can be specified. Moreover, ArtistAlleyModeration.razor was cleaned up a bit
Metawolve
reviewed
Sep 4, 2024
…specific-users-as-well-as-disabling-registration' into 198-Artist-Alley-allow-blocking-specific-users-as-well-as-disabling-registration # Conflicts: # src/Eurofurence.App.Backoffice/Pages/ArtistAlleyModeration.razor
…rs-as-well-as-disabling-registration # Conflicts: # src/Eurofurence.App.Backoffice/Components/ArtistAlleyApplicationDialog.razor # src/Eurofurence.App.Backoffice/Pages/ArtistAlleyModeration.razor
…well as disabling registration (#198) Done some refactoring here: + UserStatus* was renamed to a more meaningfully UserPenalty* + Comments where written + A loading animation was added to the data grid when fetching the data
… as disabling registration (#198) Added more documentation
…as disabling registration (#198) Fixed broken migration and wrong API endpoint
… as disabling registration (#198) Users can now banned from the detail dialog of an application as well
Fenrikur
requested changes
Sep 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's currently also no way to list current penalties and potentially revoke them?
The migrations should also be compacted into a single one for a change like this.
src/Eurofurence.App.Backoffice/Components/ArtistAlleyApplicationDialog.razor
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Backoffice/Components/ArtistAlleyApplicationDialog.razor
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Backoffice/Components/ArtistAlleyApplicationDialog.razor
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Domain.Model/ArtistsAlley/UserStatus/ArtistAlleyUserPenaltyChangedRecord.cs
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Server.Web/Controllers/ArtistsAlleyController.cs
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Server.Web/Controllers/ArtistsAlleyController.cs
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Server.Web/Controllers/ArtistsAlleyController.cs
Outdated
Show resolved
Hide resolved
src/Eurofurence.App.Server.Web/Controllers/ArtistsAlleyController.cs
Outdated
Show resolved
Hide resolved
Fenrikur
approved these changes
Sep 8, 2024
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.
This PR fixes #198
Users can now be blocked from submitting new artist alley registrations.