Skip to content

fix: misleading spec fetch error message in example.php#1478

Open
Parship12 wants to merge 1 commit intoappwrite:masterfrom
Parship12:misleading-err-msg
Open

fix: misleading spec fetch error message in example.php#1478
Parship12 wants to merge 1 commit intoappwrite:masterfrom
Parship12:misleading-err-msg

Conversation

@Parship12
Copy link
Copy Markdown
Contributor

@Parship12 Parship12 commented Apr 25, 2026

$spec = getSSLPage("https://raw.githubusercontent.com/appwrite/specs/main/specs/{$version}/swagger2-{$version}-{$platform}.json");

raw.githubusercontent.com is Github's CDN for raw file content... it has nothing to do with an Appwrite server. So, the error msg now accurately tells us where the fetch actually failed.

It isn't wrong, it's just misleading in the context of this codebase where "Appwrite server" has a very specific meaning to contributors. But now the fix will show it's a github fetch that failed, not something like the appwrite api being down.

Signed-off-by: Parship Chowdhury <parshipchowdhury@gmail.com>
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 25, 2026

Greptile Summary

This PR fixes a misleading error message in example.php where a failed spec fetch was attributed to "Appwrite server" when the request actually targets raw.githubusercontent.com. The new message correctly names GitHub and includes version and platform interpolated values to aid debugging.

Confidence Score: 5/5

Safe to merge — single-line error message fix with no logic or security implications.

The change is purely a string correction in an error message; the logic, fetch URL, and surrounding code are untouched. No bugs or regressions introduced.

No files require special attention.

Important Files Changed

Filename Overview
example.php Error message corrected to reference GitHub instead of Appwrite server, with version/platform context added for easier debugging.

Reviews (1): Last reviewed commit: "change the err msg" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant