]I have a doubt. I was using Appwrite in version 1.3 and updated to version 1.4. I would like to know if there have been changes to the structure or if I can use the functions from version 1.3 in version 1.4?
function 1.3
module.exports = async function (req, res) {
const client = new Client()
.setEndpoint(req.variables['APPWRITE_FUNCTION_ENDPOINT'])
.setProject(req.variables['APPWRITE_FUNCTION_PROJECT_ID'])
.setKey(req.variables['APPWRITE_FUNCTION_API_KEY'])
.setSelfSigned(true);
const databases = new Databases(client);
const reqPayload = req.payload;
const { id_order} = JSON.parse(reqPayload);
}```
Or do I really need to put it in this model below
function 1.4
module.exports = async function (context) { const client = new Client() .setEndpoint(process.env["APPWRITE_FUNCTION_ENDPOINT"]) .setProject(process.env["APPWRITE_FUNCTION_PROJECT_ID"]) .setKey(process.env["APPWRITE_FUNCTION_API_KEY"]) .setSelfSigned(true);
const databases = new Databases(client); const body = context.req.bodyRaw; ```
Appwrite 1.4 will keep executing function from 1.3, however there are many great changes in 1.4 that worth to upgrade your function syntax, you can check detailed information from here:
https://appwrite.io/docs/products/functions/development#upgrade
But could I run the 1.3 functions in 1.4.2 without changing the syntax? For example, could I continue to get environment variables in Appwrite 1.4 using req.variables? Or even getting the body that comes in the request using req.payload? Or would I actually need to change to process.env and req.body/bodyRaw
I didn't find anything about this in the documentation.
Yes, you could still run the 1.3 function without any change after upgrade
Recommended threads
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region