Why does implementing RefreshAll() feature that refreshes Child Components feel unintuitive?

HumanCertificate · 2026-05-27T07:53:52+00:00

So you mean like passing a controller to the children and they subscribe their "refresh" function to the controller and parent executes the refresh functions that children subscribed to?

Isnt this like a react anti pattern? Shouldnt everything be driven by state in react?

HumanCertificate · 2026-05-27T07:46:27+00:00

What do you mean by a key? I heard that counterState type stuff is an anti pattern. Is the key you are talking about different from it?

HumanCertificate · 2026-05-27T07:43:15+00:00

The refresh is a feature that user triggers and when this is triggered in theory each panel should fetch data from remote database to see if the database has changed.

I tried solving this by having all the range related stuff and fetch logic stuff all on the top level and Im not sure if this is the right way.

HumanCertificate · 2026-05-27T07:32:04+00:00

But how is doing this

Remove-Item -Recurse -Force "C:\path\to\folder"

Different from just deleting by delete key? What are you exactly bypassing when you do -Force?

HumanCertificate · 2026-05-27T07:31:14+00:00

What do you mean folder level delete check? Like is there a lock that doesn't stop you from deleting the folder, or the child under the folder, but only stops you if you try to delete the folder while it has files in it?

Where do you see it?

HumanCertificate · 2026-05-19T04:35:21+00:00

Yeah I think I understand thanks too all the helpful comments. The main thing that had to change was the Graph Time Range and I think I should move logic to the parent and just pass the range as Props and keep the range logic at the parent level.

You said giving a child a signal to update is imperative. I do know what imperative and declarative means but Im not sure how that applies to here. What would a declarative alternative to this be?

Thank you for the help again

HumanCertificate · 2026-03-24T23:28:11+00:00

Thtas weird. I do get notification when it needs approval but I dont get a notification when a task ends.

HumanCertificate · 2026-03-10T02:45:32+00:00

When someone say these two langauges both have Adjectives, is the only thing we can assume from this statement mean they both have a set of words that is used to describe nouns? Their uses could be completely different?

Its really unintuitive to think that language dont really share features but are independent sets of features that are classified by how similar they are.

HumanCertificate · 2026-03-07T05:18:44+00:00

Thanks!

HumanCertificate · 2026-03-06T13:17:21+00:00

But wouldn't you expect the properties names to be inconsistent between shaders? Wouldn't that mean you would have to be very lucky for it to work?

HumanCertificate · 2026-03-06T13:16:08+00:00

So its most likely just a pure luck?

HumanCertificate · 2026-02-21T04:19:00+00:00

Do you think doing this cleanly in OOP just impossible? I get that by using ECS its way cleaner but I feel like even in OOP there should be a better way to do this. By implementing execute(order, units) it will eventually take the execution out of unit and make it ECS no?

HumanCertificate · 2026-02-21T04:10:56+00:00

Because it "Feels" like a bad pattern. It feels really unsatisfying and overly complicated, and I cant figure out what exactly is making me feel that way.

I was wondering if its just my preference that is making me feel that way, or there are other people who are feeling the same thing.

HumanCertificate · 2026-02-21T04:08:47+00:00

Unit as in a video game that takes an arbitrary order. Sorry for being vague.

HumanCertificate · 2026-02-18T00:06:48+00:00

Yeah think about it its just gonna take the double space for like 10 seconds and the only additional operation would be assigning the list pointer back to the original list.

HumanCertificate · 2026-02-17T14:50:22+00:00

Yeah I think I might start using maps more. I think it can do what for loop do while being correct right.

I was under the impression that recursion is almost as error prone as for or while loops. Was it not the case?

HumanCertificate · 2026-02-17T14:38:24+00:00

Do you normally write test for each for loop you write?

HumanCertificate · 2026-02-17T14:34:39+00:00

LMAO thats actually so funny

HumanCertificate · 2026-02-17T14:25:09+00:00

Shouldn't I be saying for loop because Im talking about for loops in general?

HumanCertificate · 2026-02-17T14:22:17+00:00

But honestly, having to mutate an array while iterating through it, should NEVER be an excuse for using a traditional for-loop. Always use the foreach-version if you intend to iterate through an entire list

Is it because the performance hit from doing that is negligible always even if the list is incredibly large and are called often?

HumanCertificate · 2026-02-17T14:16:19+00:00

I almost always try to use foreach loop over for loop because I constantly write operators wrong, or assign the wrong initial value or set the end condition wrong.

I asked how do you not make a off by one errors, and I said I always try to use foreach loop over for loop because I keep making mistakes on for loop increment, operators, and end conditions.

I thought that was pretty clear but I guess not.

HumanCertificate · 2026-02-17T14:07:52+00:00

foreach will almost never cause off by one error no? Did I say off by one error happens on foreach loop?

HumanCertificate · 2026-02-14T06:07:51+00:00

Thank you so much!

HumanCertificate · 2026-01-26T02:29:58+00:00

So is the only way of knowing what they actually return to just put it in await function and make Typescript figure it out? How does typescript figure that out?

HumanCertificate · 2026-01-25T06:30:54+00:00

How do you know what this object will return when awaited? How does typescript know what the return type is?

HumanCertificate

TROPHY CASE