3 ms·
> We do have plans to improve the current database trigger behavior. Will share more updates on this in the coming months. Excited to hear more! Being able to
by cjonas 3y ago
> We do have plans to improve the current database trigger behavior. Will share more updates on this in the coming months.
Excited to hear more! Being able to trigger functions from DB & cron triggers without having to hardcode a secret (which causes them to end up in migrations files) will be a huge improvement.
> Can you explain what do you mean by template URLs?
Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw.
> Source maps, is it broken during local dev or when you deploy the function?
Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338 https://github.com/supabase/cli/issues/1338
"Source maps" (does deno actually use source maps?) ARE broken as well. EG: The line numbers in runtime don't line up with the function code in the IDE or even that is in the docker volume.
- laktek 3y ago> Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw. Good point! will update the docs. > Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338 https://github.com/supabase/cli/issues/1338 I'll take a look at this issue. We've improved import map resolution in the last couple of CLI releases. But it looks like there are more edge cases.