public/owltide
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages 1 Wiki Activity Actions
owltide/server/api/auth/account.patch.ts

74 lines
2.1 KiB
TypeScript
Raw Normal View History

Add delete account function
2025-03-07 22:28:55 +01:00
import { readAccounts, writeAccounts } from "~/server/database";
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
import { DateTime } from "luxon";
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
import { apiAccountPatchSchema } from "~/shared/types/api";
import { z } from "zod/v4-mini";
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
export default defineEventHandler(async (event) => {
Rename AcountSession to ServerSession Start the work of clearly distingushing client side types, server side types and types shared over the API by renaming "AccountSession" and "Session" names used on the server to "ServerSession".
2025-06-09 16:51:05 +02:00
const session = await requireServerSession(event);
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
const { success, error, data: patch } = apiAccountPatchSchema.safeParse(await readBody(event));
if (!success) {
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
throw createError({
status: 400,
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
statusText: "Bad Request",
message: z.prettifyError(error),
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
});
}
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
if (patch.timezone?.length) {
const zonedTime = DateTime.local({ locale: "en-US" }).setZone(patch.timezone);
if (!zonedTime.isValid) {
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
throw createError({
status: 400,
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
message: "Invalid timezone: " + zonedTime.invalidExplanation,
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
});
}
}
Add per account locale setting Add a per user account setting for the locale so that the server can correctly render pages with localized time formatting.
2025-06-13 21:50:22 +02:00
if (patch.locale?.length) {
const locale = DateTime.local({ locale: patch.locale }).resolvedLocaleOptions().locale;
if (locale !== patch.locale) {
throw createError({
status: 400,
message: `Invalid locale: the locale "${patch.locale}" is not supported (was treated as "${locale}")`
});
}
}
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
const accounts = await readAccounts();
const sessionAccount = accounts.find(account => account.id === session.accountId);
if (!sessionAccount) {
throw Error("Account does not exist");
}
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
if (patch.interestedEventIds !== undefined) {
if (patch.interestedEventIds.length) {
sessionAccount.interestedEventIds = patch.interestedEventIds;
} else {
delete sessionAccount.interestedEventIds;
}
}
if (patch.interestedEventSlotIds !== undefined) {
if (patch.interestedEventSlotIds.length) {
sessionAccount.interestedEventSlotIds = patch.interestedEventSlotIds;
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
} else {
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
delete sessionAccount.interestedEventSlotIds;
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
}
}
Refactor API types and sync logic Rename and refactor the types passed over the API to be based on an entity that's either living or a tombstone. A living entity has a deleted property that's either undefined or false, while a tombstone has a deleted property set to true. All entities have a numeric id and an updatedAt timestamp. To sync entities, an array of replacements are passed around. Living entities are replaced with tombstones when they're deleted. And tombstones are replaced with living entities when restored.
2025-06-11 21:05:17 +02:00
if (patch.timezone !== undefined) {
if (patch.timezone)
sessionAccount.timezone = patch.timezone;
Add per account overridable timezone setting To make it possible to render the timetable in the user's local time we need to know the timezone to render it in on the server. Otherwise there will be hydration errors and paint flashing as the client renders a different timezone. Add a server global default timezone that can be overriden on a per-account bases to prepare for timezone handling the timetable.
2025-03-09 15:53:51 +01:00
else
delete sessionAccount.timezone;
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
}
Add per account locale setting Add a per user account setting for the locale so that the server can correctly render pages with localized time formatting.
2025-06-13 21:50:22 +02:00
if (patch.locale !== undefined) {
if (patch.locale)
sessionAccount.locale = patch.locale;
else
delete sessionAccount.locale;
}
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
await writeAccounts(accounts);
Add delete account function
2025-03-07 22:28:55 +01:00
// Update Schedule counts.
await updateScheduleInterestedCounts(accounts);
Track which account is interested in which events Store a list of ids of events and slots that accounts have marked as being interested in, and show aggeregate counts in the schedule.
2025-03-07 20:15:41 +01:00
})
Reference in a new issue Copy permalink