jeff
jeff
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
Huge thanks to Erquhart for taking the time to figure this out and explain this to me! Once Convex introduces community medals... I have a recommendation! 🎖️
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
yeah, but do we need to become discord friends ios what I meant
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
do we need to become friends? 😄
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
kk ready
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
similarly, lemme get a glass of water 1 min
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
screenshare etc.
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
(also happy to have a brief call, capped at max 30' though, if you wanna do some live debugging)
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
I, unfortunately, am also a nerd who needs to get to the bottom of this so I can sleep tonight 😛
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
convex/payment.ts:127:14 - error TS7022: 'verifyPayment' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

127 export const verifyPayment = action({
~~~~~~~~~~~~~
convex/payment.ts:146:15 - error TS7022: 'paymentIdAndRequest' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

146 const paymentIdAndRequest = await ctx.runQuery(internal.payment_utils.getPaymentIdAndRequest, {...args});
~~~~~~~~~~~~~~~~~~~

convex/payment.ts:147:27 - error TS7022: 'request' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

147 const {paymentId, request} = paymentIdAndRequest;
~~~~~~~

convex/payment.ts:153:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

153 const requestStatus = request.status;
~~~~~~~~~~~~~

Found 4 errors in the same file, starting at: convex/payment.ts:127
convex/payment.ts:127:14 - error TS7022: 'verifyPayment' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

127 export const verifyPayment = action({
~~~~~~~~~~~~~
convex/payment.ts:146:15 - error TS7022: 'paymentIdAndRequest' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

146 const paymentIdAndRequest = await ctx.runQuery(internal.payment_utils.getPaymentIdAndRequest, {...args});
~~~~~~~~~~~~~~~~~~~

convex/payment.ts:147:27 - error TS7022: 'request' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

147 const {paymentId, request} = paymentIdAndRequest;
~~~~~~~

convex/payment.ts:153:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

153 const requestStatus = request.status;
~~~~~~~~~~~~~

Found 4 errors in the same file, starting at: convex/payment.ts:127
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
still errors
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
const paymentIdAndRequest = await ctx.runQuery(internal.payment_utils.getPaymentIdAndRequest, {...args});
const {paymentId, request} = paymentIdAndRequest;
const paymentIdAndRequest = await ctx.runQuery(internal.payment_utils.getPaymentIdAndRequest, {...args});
const {paymentId, request} = paymentIdAndRequest;
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
ok 2 mins
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
(I am new to both JS and TS)
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
as in const both = runQuery(... and then destructuring both?
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
here's all 3:
convex/payment.ts:127:14 - error TS7022: 'verifyPayment' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

127 export const verifyPayment = action({
~~~~~~~~~~~~~
convex/payment.ts:146:27 - error TS7022: 'request' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

146 const {paymentId, request}: {paymentId: Id<"payments">; request: Doc<"requests">} = await ctx.runQuery(
~~~~~~~

convex/payment.ts:155:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

155 const requestStatus = request.status;
~~~~~~~~~~~~~

Found 3 errors in the same file, starting at: convex/payment.ts:127
convex/payment.ts:127:14 - error TS7022: 'verifyPayment' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

127 export const verifyPayment = action({
~~~~~~~~~~~~~
convex/payment.ts:146:27 - error TS7022: 'request' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

146 const {paymentId, request}: {paymentId: Id<"payments">; request: Doc<"requests">} = await ctx.runQuery(
~~~~~~~

convex/payment.ts:155:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

155 const requestStatus = request.status;
~~~~~~~~~~~~~

Found 3 errors in the same file, starting at: convex/payment.ts:127
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
convex/payment.ts:155:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

155 const requestStatus = request.status;
~~~~~~~~~~~~~
convex/payment.ts:155:15 - error TS7022: 'requestStatus' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

155 const requestStatus = request.status;
~~~~~~~~~~~~~
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
No description
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
that's exactl;y what I did, before the explicit type annotation
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
the return value of one function is returned in the encapsulating function ... that's just standard procedural programming, no? XD
38 replies
CCConvex Community
Created by jeff on 3/6/2024 in #support-community
Surely a bug (with TypeScript fanciness) ?
thanks for your help ❤️ I can unequivocally say, though, that I do not remotely understand this.
38 replies