Have options as dependancy in useEffect in sharedFeatures.js without spaming API calls #658

New issue

Open

opened 2026-04-30 06:51:44 +00:00 by c24danli · 2 comments

c24danli commented

2026-04-30 06:51:44 +00:00

Collaborator

At the moment we dont have options as a dependancy in the useEffect in the file sharedFeatures.js.
It can run but have errors, we need to figure out the correct way to use options and have it as a dependancy while not uppdating API calls all the time.

At the moment we dont have options as a dependancy in the useEffect in the file sharedFeatures.js. It can run but have errors, we need to figure out the correct way to use options and have it as a dependancy while not uppdating API calls all the time.

c24danli was assigned by c24elipe

2026-04-30 08:01:09 +00:00

c24danli added the

bug

help wanted

labels

2026-05-05 09:52:50 +00:00

c24danli removed their assignment

2026-05-05 09:53:00 +00:00

c24danli added the

unassigned

label

2026-05-06 10:03:11 +00:00

c24danli commented

2026-05-11 09:10:43 +00:00

Author

Collaborator

At the bottom of useEffect
we currently have
}, [API_URL, dependency]);
but we should have
}, [API_URL, dependency, options]);
As we use the options varible in the function.
If we just add it as is the options variable gets refreshed all the time and send api calls.

At the bottom of useEffect we currently have `}, [API_URL, dependency]);` but we should have `}, [API_URL, dependency, options]);` As we use the options varible in the function. If we just add it as is the options variable gets refreshed all the time and send api calls. ![image](/attachments/3503a9ab-1cfe-4ffa-b455-a08faff080a8)

image.png

45 KiB