Skip to content

refactor(advancement): overhaul notification page - #214

Merged
theEvilReaper merged 7 commits into
developfrom
feat/advancement
Oct 8, 2026
Merged

theEvilReaper merged 7 commits into
developfrom
feat/advancement

Conversation

@theEvilReaper

@theEvilReaper theEvilReaper commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Proposed changes

There was a decision to transform the NotificationEntity into a full Advancement replica. This has already been implemented in the backend, and the pull request adds the frontend part.

Types of changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING.md
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@theEvilReaper
theEvilReaper merged commit 379ae43 into develop Oct 8, 2026
19 checks passed
@theEvilReaper
theEvilReaper deleted the feat/advancement branch October 8, 2026 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant