Closed stoft closed 3 months ago
Interesting! It's neat to see what kinds of things other people are doing with it.
Just a thought: is it possible that your GitHub Workflow Action is using a database where you haven't applied migration scripts yet? That's the only reason I can think that there would be no application tables.
Next thought: Are you using more than one .toml config file? (I'm wondering if you might have table filters specified in one config but not another). If so, there is an option to specify which .toml file is used.
setting the wrong password in the toml causes SqlHydra.Cli to throw an error
That sounds like the expected behavior.
Thank you @JordanMarr ! As it turns out the migrations, and our integration tests, were running correctly but in an unexpected schema (public
instead of our specific schema). All good now! It's a shared code base with TS and F#, now we can get a heads up during the build that a migration on the TS side may have broken something on the F# side.
An improvement in SqlHydra could be to warn when an include filter has zero hits. This would imply that something is not as expected or no longer needed. Feel free to close this issue unless you want to convert it to a feature request. š
That's pretty cool. Are you using Fable to generate your TS types?
Are you using Fable to generate your TS types?
No, it's a service completely written in TS that we're now adding F# code to. We have other services in F# and want to gently start moving away from TS.
I'm closing this issue now as resolved. Thank you so much for the help!
Resolved by https://github.com/JordanMarr/SqlHydra/issues/87#issuecomment-1999889588
Thanks. i may add a message if all records are filtered out.
I'm mostly in need of rubber ducking here and ideas on how to debug this I think and don't know where else to turn. š
I've added a GitHub workflow action that will auto-generate types and
git diff
them against the types in the PR with the goal of failing the build if there is a diff.Problem: for some reason the generator is not generating the types for the tables, only the general types.
Environment:
Debugging and known so far:
toml
causes SqlHydra.Cli to throw an errorWorkflow steps:
I've added the
ls -l
just to show the size diff before and after.make generate-db-types
is equal todotnet sqlhydra npgsql --project ...
Output:
Here we can see the size has more than halved and the diff is in reality about 200 lines removed.
Thanks for a great tool! Any ideas on how to debug this would be greatly appreciated. ā¤ļø