TypeScript
import { initializeAppwriteClient } from "./appwriteConfig.js";
import router from "./apiRoutes.js";
import { isUpdateEvent } from "./util/createTeamUtil.js";
export default async ({ req, res, log, error }: any) => {
const triggered = req.headers["x-appwrite-trigger"];
const path = req.path;
const method = req.method;
const eventType = req.headers["x-appwrite-event"];
log(`Request received by ${path} with method ${method}`);
log(`Triggered type: ${triggered}`);
log(`Event type: ${eventType}`);
try {
if (triggered === "event" && path === "/" && method === "POST") {
if (isUpdateEvent(req, eventType)) {
req.path = "/v1/teams";
}
}
const client = initializeAppwriteClient();
return res.send(
{
message: "Hello from Appwrite Cloud Functions!",
},
200,
{
"content-type": "application/json",
}
);
return await router.handleRequest({ req, res, log, error, client });
} catch (e) {
// Handle initialization errors
error(`Initialization failed: ${e.message}`);
return res.send(
{
message: `Initialization failed: ${e.message}`,
},
500,
{
"content-type": "application/json",
}
);
}
};
Focus on this code:
TypeScript
return res.send(
{
message: "Hello from Appwrite Cloud Functions!",
},
200,
{
"content-type": "application/json",
}
);
as you can see in that code I am sending an json, now the result gives me an object
TL;DR
The user was experiencing an issue where the result of their code was returning an object instead of JSON. They mentioned using JSON.stringify to solve the problem.I solved btw, I used JSON stringify, but its weird in javascript it is fine without using JSON stringify
Recommended threads
- router_deployment_not_found
I updated my function a few times and now i am getting the error: router_deployment_not_found I even reverted back to my original code but i am still getting th...
- Cloud function deploy stucks in processi...
Been trying for the last hours to deploy my function but for whatever reason, alwasy stuck on processing!
- [SOLVED] curl error Number: 6 — function...
Hello, I invested a lot of time in this error in a fresh install of appwrite 1.8.1 and lasted until fix, this if for helping anyone that can have the same weird...