The DBT equivalent of this integration computes a code version hash for each model it is producing an asset for. Each time the underlying model code changes, it causes the code version in Dagster to update. This allows the UI to clearly show which assets have had their code change since last materialization, making it easy to know which assets need to be run.
The translator could take care of this quite easily. The IntermediateAssetOut could be updated to take in a code version. The code version can be computed in a function on SQLMeshDagsterTranslator allowing it to be overridden by user's custom translator.
The DBT equivalent of this integration computes a code version hash for each model it is producing an asset for. Each time the underlying model code changes, it causes the code version in Dagster to update. This allows the UI to clearly show which assets have had their code change since last materialization, making it easy to know which assets need to be run.
The translator could take care of this quite easily. The IntermediateAssetOut could be updated to take in a code version. The code version can be computed in a function on SQLMeshDagsterTranslator allowing it to be overridden by user's custom translator.