Isomorphic JavaScript client for Supabase providing authentication, database, real-time, storage, and edge functions capabilities.
89
{
"context": "This criteria evaluates how well the engineer uses @supabase/supabase-js edge function invocation capabilities to implement a notification service client. The focus is on proper usage of the functions.invoke() method with different body types (text and JSON) and HTTP methods.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Client initialization",
"description": "Uses createClient() to initialize a Supabase client instance with the provided serviceUrl and serviceKey parameters",
"max_score": 15
},
{
"name": "Text body invocation",
"description": "Uses functions.invoke() to send text notifications by passing a string body in the options parameter for sendTextNotification()",
"max_score": 25
},
{
"name": "JSON body invocation",
"description": "Uses functions.invoke() to send structured notifications by passing a JSON/object body in the options parameter for sendStructuredNotification()",
"max_score": 25
},
{
"name": "HTTP method configuration",
"description": "Properly configures the method option in functions.invoke() (e.g., POST for sending, GET for retrieving status)",
"max_score": 15
},
{
"name": "Response handling",
"description": "Correctly accesses the data and error fields from the FunctionInvokeResponse returned by functions.invoke()",
"max_score": 10
},
{
"name": "Error handling",
"description": "Properly handles error responses from functions.invoke() and returns appropriate error messages in the specified format",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-supabase--supabase-jsevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10