I've spent the better part of the last 2 weeks trying to get Xdebug setup and working with Appwrite locally.
I realized the launch.json specified in the CONTRIBUTING.md(https://github.com/appwrite/appwrite/blob/main/CONTRIBUTING.md#vs-code-launch-configuration) wasn't quiet right. At least for me.
This is the configuration that was specified.
{
"name": "Listen for Xdebug",
"type": "php",
"request": "launch",
"port": 9005,
"pathMappings": {
"/usr/src/code": "${workspaceRoot}"
}
}
It appears "${workspaceRoot}" has been deprecated in favour of "${workspaceFolder}" in VSCode.
I'd like to know if there is a reason "${workspaceRoot}" is still maintained in the guide, and if "${workspaceFolder}" is indeed the right one, can I create an issue on it and possible even create a PR to have it updated??
Recommended threads
- is `account.get()` safe to be used in th...
I want to user's `id` for authentication. However, a while ago I was told in this server not to use `account.get()` and instead add user preferences for that us...
- mcp-server-appwrite 0.4 fails on startup...
I’m trying to use `mcp-server-appwrite` against Appwrite Cloud and the server authenticates successfully, but fails during startup validation when probing `tabl...
- open runtime version lacks behind
open runtime version in appwrite CLI is v4 while the hosted runtimes use v5, this mismatch does not permit to debug locally functions using recent runtimes (li...