Skip to content
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

Deployment #1449

Merged
merged 85 commits into from
May 6, 2024
Merged

Deployment #1449

merged 85 commits into from
May 6, 2024

Conversation

AndreasHuber and others added 30 commits April 25, 2024 18:42
* DB-Layer only responds with valid uuids currently
* In the future this is not needed once the sql query is inside api due
  to proper filter in the query
DB-Layer should not respond with an invalid alias (in the long run we
will have control over it anyways)
This test is not needed after we migrate the DB layer into the API
Actually this is a better name IMHO :-)
refactor: Rename "schema/notification" to "schema/events"
refactor: Split code for events and notifications
refactor(event): Move events query into API
refactor(event)!: Remove AbstractUuid.events and User.eventsByUser
kulla and others added 29 commits May 3, 2024 23:58
chore: Enable source-maps in "yarn start"
refactor(database): Add fetchOptional() + better transaction handling
User management for local development
…tabase-layer

Migrate set thread status from database layer
…s for an array of IDs instead of only a single ID in order to have a test for what was the first error during implementation
refactor(subject): use database directly for subjects query
test(set-thread-status): remove dependency of test on certain ID
@hugotiburtino hugotiburtino merged commit 145e80c into production May 6, 2024
18 checks passed
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.

4 participants