You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Behind the scenes I expected it was using the default value of "pgmigrations", same as the CLI.
It was actually coercing the missing value to a string and creating a migrations table named "undefined". Probably not harmful (it certainly wasn't in my case), but a little surprising. Feels more like an unexpected side-effect than a deliberate choice.
Description
Discovered that
migrationsTable
was actually a required property when converting some JavaScript files to TypeScript.I had been calling
runner()
without providingmigrationsTable
and it seemed to work fine:Behind the scenes I expected it was using the default value of
"pgmigrations"
, same as the CLI.It was actually coercing the missing value to a string and creating a migrations table named
"undefined"
. Probably not harmful (it certainly wasn't in my case), but a little surprising. Feels more like an unexpected side-effect than a deliberate choice.Suggested solution
Either
"pgmigrations"
, similar to CLI. Argument against this here (#544).migrationsTable
is missing.Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: