Closed mre closed 1 year ago
I would suggest to add start/end as params to be more flexible. the user can then decide if just one day is needed or a range should be fetched from the API
tackling this next
could we use markdown/yaml/frontmatter/json to define the SQL queries and metadata? would be the advantage that we do not have to invent our own format?
I think we can. Let's introduce the date parameters manually first and then consider rewriting it to dbt. I have a feeling that it will simplify things a lot.
We decided that we'll try to use SQL variables, which are a nice tradeoff between customizability and fully native SQL syntax.
in progress openpodcast/api#67
Example: http://localhost/analytics/v1/podcastGender?date=2023-02-12