The following command outputs the schema in the specified format
dlt local schema --format FORMAT SCHEMA_FILE_PATH
However, the latest changes added a message that is printed whenever dlt is called instead of dlthub
NOTE: Please use dlthub as top level command. Check `dlthub local --help` for former dlt commands. Falling back to dlthub command set.
This breaks the ability to pipe commands and push values to a file. For example, this will produce invalid JSON
Input: user command
dlt local schema --format json SCHEMA_FILE_PATH > my_schema.json
Output: content of my_schema.json is invalid json because it captures NOTE: message
NOTE: Please use dlthub as top level command. Check `dlthub local --help` for former dlt commands. Falling back to dlthub command set.
{
"version": 2,
"version_hash": "bsxTAxmbRGV29fefv3NIfsTHr8meNMN4j8wAcwFmCVQ=",
"engine_version": 11,
"name": "sql_database",
...
}
The following command outputs the schema in the specified format
dlt local schema --format FORMAT SCHEMA_FILE_PATHHowever, the latest changes added a message that is printed whenever
dltis called instead ofdlthubThis breaks the ability to pipe commands and push values to a file. For example, this will produce invalid JSON
Input: user command
Output: content of
my_schema.jsonis invalid json because it capturesNOTE:message