Closed burnash closed 3 days ago
Name | Link |
---|---|
Latest commit | 9ad11ea6d9a0a678b5b52f42820356fe7183f095 |
Latest deploy log | https://app.netlify.com/sites/dlt-hub-docs/deploys/6733bd7c20a0b00008425236 |
@burnash from what I can tell this approach makes sense. What I would do: extend the dlt init tests to check the created requirements files and also do a manual test with each core source just to be sure it actually works.
What I would do: extend the dlt init tests to check the created requirements files and also do a manual test with each core source just to be sure it actually works.
Thanks @sh-rp, test are in 31bb59c
Implements #1794
Not sure if this is the best way to do it as there's a lot of implicit stuff and assumptions. Mostly this is to handle missing extra for the
rest_api
source.The alternatives to reading package metadata are:
requirements.txt
as in verified sources and handle it the same way.