Why is the numerical value of "pendingWorkPriority" inversely proportional to its meaning? about react-fiber-architecture HOT 4 OPEN

I was confused by this too until I thought of it as the priority that’s assigned to bugs. a P1 bug would be of the “all hands on deck” type, whereas a P5 is “meh, we’ll probably never get around to it”. see here for one description of priority bug rankings.

from react-fiber-architecture.

I was confused by this too until I thought of it as the priority that’s assigned to bugs. a P1 bug would be of the “all hands on deck” type, whereas a P5 is “meh, we’ll probably never get around to it”. see here for one description of priority bug rankings.

@abigsmall Except for NoWork, which should be 6 following this logic ;)

from react-fiber-architecture.

This is indeed a potential confusion that we see in the current code: https://github.com/facebook/react/blob/f53854424b33692907234fe7a1f80b888fd80751/src/renderers/shared/fiber/ReactFiberScheduler.js#L427

I’m also curious about this design decision.

from react-fiber-architecture.

@Prinzhorn nah, the context of the logic is “the priority that’s assigned to bugs”. a P5 bug still has a modicum of possibility of being fixed, whereas a bug that will absolutely not be fixed will not be given any priority at all. I think that falls in line with a priority value of 0, essentially. perhaps a bit of a stretch, but it makes sense to me :)

from react-fiber-architecture.