nut
any way to update a signal without it causing a reactive update?
anyways, I figured out a Band-Aid solution so it's okay you don't have to waste any more time thinking about this, I was just wondering if there was a trivial solution like an untrack for writing
16 replies
any way to update a signal without it causing a reactive update?
The issue with that approach is that if a user is directly linked to the entry page, it should fetch the listings such that when the user goes back they don't have to do another fetch. in addition, I cannot use a regular variable on this page because I want to have a reactive response depending on whether or not the data being fetched is currently loading or potentially is in an error state
16 replies
any way to update a signal without it causing a reactive update?
however, when you go back because the route re-renders as long as we update the original signal we don't have to refetch the data and also the route renders with the updated entry
16 replies
any way to update a signal without it causing a reactive update?
I have a signal on a previous page that has a list of completed entries and then on the entry page which is on a separate route when I complete one. I want to update the original signal so that when the user hits the back button that entry is completed. however, the entries are a resource that can either be in a loading State, a data state, or an error state. and currently if I update an entry to be completed on the entry page by modifying the original signal list then the entire page re-renders but I do not want this because I want it to maintain its current state
16 replies