1. Feedback on Dagster’s redundant Public APIs a. This is related to 2 overlapping Dagster Constructs

@asset_sensor

+

AssetSensorDefinition

and

@multi_asset_sensor

+

MultiAssetSensorDefinition

b. Why are there two constructs, instead where one could suffice? the

@multi_asset_sensor

should be the actual

@asset_sensor

2. Probably opinionated feedback on the naming Dagster public APIs (one of) a.

monitored_assets

five stars for it, very straightforward to understand b.

request_asset

does not gel well, I have to read documentation to grasp that instead of job there is directly a way to materialize an asset directly, but I can only provide AssetSelection, instead of AssetKeys like

monitored_assets

c. Knowing that Sensors are between 2 executable components, first that finishes its execution, second is the one that is supposed to be triggered, and with that in mind

@asset_sensor

, if it takes

upstream_assets

(AssetKeys|AssetSelections) and `downstream_assets`(AssetKeys|AssetSelections) makes it intuitive for developer to code it