Open riyaz-ali opened 1 year ago
is this completed ? otherwise lets change this to draft :)
My reason behind having a custom type (and not simply using the underlying table definition) is that I don't want to expose the "internals" of the sqlq
schema to the user. The only way I found with custom functions is to add a custom type and return that.
Just want to check in here on what the go-forward should be for this PR. Are we okay with ENUMs once we've documented them a bit internally as to why/where we'd choose to use them?
We are going to convert this to a draft PR as not all of the views we need have been identified and added. We will create a list of the views we need and start working to add them to this PR as we continue to work on them. This will not be a blocking draft as we will continue to work on the other issues. @riyaz-ali will also still need to document ENUMS in notion.
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:
This PR adds support for inspecting and querying meta-information from sqlq. Closes #22