안녕하세요 벨로퍼트님.
벨로퍼트님의 리액트쿼리 훅에 대해서 많은 영감을 받아서 적용 중에 있습니다.
그러던 도중에 UseMutationOptionsOf의 Parameters부분에 문제가 생겨서 질문을 올립니다.

마지막 코드에서 () => mutate() 같은 경우 undefined로 되어서 에러가 뜹니다.
그래서 첫번째 코드와 같이 Parameters 부분을 Parameters<TAPI>[0] extends undefined ? void : Parameters<TAPI>[0] 으로 바꿔 주었습니다.
괜찮은 코드일까요?

import { AppError } from '@/lib/error';
import {
  UseInfiniteQueryOptions,
  UseMutationOptions,
  UseQueryOptions,
} from '@tanstack/react-query';

export type UseMutationOptionsOf<TAPI extends (...args: any) => any> =
  UseMutationOptions<
    Awaited<ReturnType<TAPI>>,
    AppError,
    Parameters<TAPI>[0] extends undefined ? void : Parameters<TAPI>[0]
  >;

import type { AuthParams } from '@/lib/types';
import apiClient from './apiClient';

const AuthAPI = {
  logout: async () => {
    const { data } = await apiClient.delete<void>('/auth/logout');
    return data;
  },
};

export default AuthAPI;

import AuthAPI from '@/lib/api/auth';
import { useMutation } from '@tanstack/react-query';
import type { UseMutationOptionsOf } from '@/hooks/queries/types';

const useLogout = (
  options: UseMutationOptionsOf<typeof AuthAPI.logout> = {},
) => {
  return useMutation(AuthAPI.logout, options);
};

export default useLogout;

const { mutate } = useLogout({
    onSuccess: () => {
      window.location.href = '/';
    },
  });

<Button size="sm" color="warning" shadow onClick={() => mutate()}>
  로그아웃
</Button>

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "veltrends", schema "public" at "localhost:5434"

Error: db error: ERROR: permission denied for schema public
0: migration_core::state::ApplyMigrations
at migration-engine/core/src/state.rs:185

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

https://blog.cloudflare.com/next-on-pages/

fails to fetch

Some websites does not allow external traffic. e.g. https://earlybird.kr/2698

This issue should be resolved before introducing this service to public.
Furthermore, it would be nice to handle invalid images on client. Currently, it is looking so ugly when image loading fails.

https://blog.bitsrc.io/turbopack-is-vercels-newest-toy-better-than-vite-32abcf95ee43

When user visits item directly from external referrer (e.g. Twitter) with mobile device, the back button doesn't work (in webview) or goes back to external page.

Guiding users to homepage will be better.

https://www.veltrends.com/items/154

이런 게시글도 신고를 못합니다.
신고 버튼을 만들어주세요.

Add a tag input between title and body.
For UX, take reference from youtube studio.

New access token should be applied to the fetchClient.

• padding seems unnecessary

Gravity is too high.
Current algorithm may work if there's enough likes.

Since the token system. uses Refresh Token Rotation, a refresh token can be only used once. If a specific refresh token is used more than twice, following token will be blocked.

Current system uses a TokenRefreshScheduler which refreshes the access token before it expires.

The problem kicks in when multiple tabs are opened. All the opened tabs will eventually refresh the token at the same time, and it will cause the token to be blocked.

Possible solutions that come to my mind are:

1. Use session storage and somehow allow only one tab to refresh the token.
2. Disable the token scheduler when user loses focus, and re-enable it when user comes back to the tab. This is not a good solution because token won't refresh while user is away from the tab. To properly implement using this method, browser has to check the token expiration time by making a request to the server and refresh the token accordingly.
3. Refresh the token only when user faces 401 TokenExpiredError. Then, retry request that caused the error. This is very common solution, but it might lead to another issues (what is there are multiple concurrnet requests?), and the flow will get complicated.

I am going for first solution since it is easier to implement. However, the third solution is also a worth a try. May be I will try it later.

Seems like cookie is not cleared from www.veltrends..com

i tried using the postgres, and the frontend works like i tried to go to the login page, but in the home page it is showing some api error 500

sample https://yozm.wishket.com/magazine/detail/1686/

Dark mode will be implemented after 200+ user.

Create a checkbox that extracts title from link, since the user has to copy the title unless they are not translating it.

Setting default value of checkbox to true will be nice. Save the settings to localStorage for better UX.

Features

• Body should be optional
• Use Cloudflare R2 for images
• Add My news page: lists news that a specific user has submitted or liked
• Allow markdown in comments
• Notifications on comment
• Use popeer menu for comment modify/delete on desktop

Bug Fixes

Enhancements

• Test code for frontend
• Test code for backend
• Complete GitHub actions for ECS worker

https://www.veltrends.com/items/92

When user visits after accessToken expired, the login status is not applied to fetch result of home data. To be specific, like & bookmarks are not applied on first render. When user refreshes, login status is then applied.

This happens cause loader of homepage does not wait until token gets refreshed. Every loaders that gives different result based on login status should be patched.

It is really kind of annoying that there is no definite guide for properly setting cookie for every request. I think using createEventHandler might be a solution.. I will give a try later on.

https://www.veltrends.com/?mode=recent

현재 과거탭으로 가면,

모바일

데스크탑

위 사진과 같이 리스트가 비어있다고 뜹니다.
하지만, 다음주 버튼을 눌렀다가 다시 돌아오면, 정상적으로 화면이 표시됩니다.
예시

기본적으로 과거 탭이 잘 작동하게 버그를 고쳐주세요.