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

Analyse: fetchApi in useCallback #271

Open
tschumpr opened this issue Aug 28, 2024 · 0 comments
Open

Analyse: fetchApi in useCallback #271

tschumpr opened this issue Aug 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@tschumpr
Copy link
Contributor

So wie fetchApi aktuell definiert ist, darf man die Funktion nicht als Anhängigkeit in useEffect, etc. aufrufen, da sie ständig ändert. Damit sie nicht mehr immer geändert wird, müsste man sie in ein useCallback verpacken, was durchs async und Typing erschwert wird: async function fetchApi<T>(url: string, options: FetchParams = {}). Hier sollen nochmals die Möglichkeiten angeschaut und allenfalls umgesetzt werden.

@tschumpr tschumpr added this to the Redesign Delivery milestone Aug 28, 2024
@tschumpr tschumpr added the enhancement New feature or request label Aug 28, 2024
This was referenced Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant