-
Notifications
You must be signed in to change notification settings - Fork 135
postgres: fix tests #394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgres: fix tests #394
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
1ab3bf2 to
475eef6
Compare
75ed5d9 to
61551fb
Compare
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
…obal and a symbol. this makes sure that streamers can use in-memory event emitters and that it won't be compiled away into the different flow.js and step.js files. this was figured out when i was adding a hooks tests to world-testing. Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
we try to run them with the postgres world but it's not installed Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
…eleased. so initial attempt in postgres should reflect that. Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
Signed-off-by: Gal Schlezinger <gal@spitfire.co.il>
16fcdd8 to
c79a301
Compare
| customType, | ||
| index, | ||
| integer, | ||
| /** @deprecated: use Cbor instead */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
A few unimplemented things or Postgres-specific quirks were fixed to make sure the e2e tests now pass (at least in Next.js)
.getcalls. The CBOR columns have the same name but with a_cborsuffix, and stored asbytea(blobs), allowing us to store nested binary structures and the null byte\x00within a string.createfunction. Fixed.getWorldandsetWorldwere setting a module instance variable. This is okay generally but the problem is that we will have 3 different module scopes due to our bundling strategy that doesn't treat@workflow/coreas external:flow.jsstep.jsworkflow/apior whatever that uses them@workflow/world-postgresto all workbench/* apps, otherwise starting them with that workflow world target will failEvery breaking change I had in the e2e tests was copied (in some form) to the
@workflow/world-testing, which is a package that world authors can use to verify spec compliance. The more tests we have there, the better, as it allows our users to trust custom worlds and distribute their own ideas without being afraid of something breaking.