Update dependency convex to v1.18.0 #406
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.17.4
->1.18.0
Release Notes
get-convex/convex-js (convex)
v1.18.0
Warn on direct Convex function call. This adds a console.warn whenever a
Convex Function (mutation, query, action, internalMutation, etc.) is called
directly
because this pattern causes problems and there are straightforward
workarounds. The problems here:
validators at the function definition site.
functions may be writting assuming they will run as independent
transactions, but running these function directly breaks that assumption.
deadlocks and other bad behavior.
There are two options for how to modify your code to address the warning:
directly.
ctx.runMutation
,ctx.runQuery
, orctx.runAction()
instead ofcalling the function directly. This has more overhead (it's slower) but you
gain isolation and atomicity because it runs as a subtransaction.
See
https://docs.convex.dev/production/best-practices/#use-helper-functions-to-write-shared-code
for more.
Filter to warnings in the convex dashboard logs to see if you're using this
pattern.
For now running functions this way only logs a warning, but this pattern is
now deprecated and may be deleted in a future version.
Support for Next.js 15 and
Clerk core 2:
@clerk/nextjs@5
and@clerk/nextjs@6
are now known to work to Convex. Docs,quickstarts and templates have not yet been updated. If you're upgrading
@clerk/nextjs
from v4 or v5 be sure to follow the Clerk upgrade guides asthere are many breaking changes.
Improvements to
npx convex run
:{ name: "sshader" }
parses--identity
similar to dashboard "acting as user" feature, likenpx convex run --identity '{ name: "sshader" }'
npx convex run api.foo.bar
is equivalent tonpx convex run foo:bar
npx convex run convex/foo.ts:bar
is equivalent tonpx convex run foo:bar
npx convex run convex/foo.ts
is equivalent tonpx convex run foo:default
Allow non-JavaScript/TypeScript files in the
convex/
directory. Only .jsetc. files will be bundled and may define Convex functions points but adding a
temporary file like
convex/foo.tmp
will no longer break` the build.Fix type for FieldTypeFromFieldPath with optional objects.
Fix types when a handler returns a promise when using return value validators
with object syntax.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.