Why are Datasources attached to a store?

I couldn't find a similar question anywhere, sorry if this was already brought up.

It seems weird to me that Datasources are attached to a store in such a way that I have to call the store to execute actions. Isn't that not in-line with how Flux is designed?

Example flow when using a datasource:
Component -> Store -> Datasource -> Action -> Store -> Component

I thought with Flux ideally you'd have:
Component -> Action/Datasource -> Action -> Store -> Component

Start by tracing the Datasource, Store, Action, and Component flow described in the issue and compare it with the stated Flux model. The issue does not identify files, tests, or a concrete change, so its intended outcome and definition of done need clarification before implementation.

Written by the indexing model from the issue text.