Skip to content

feat: add extension compatibility manifest - #88

Open
TrixNEW wants to merge 1 commit into
nvms:mainfrom
TrixNEW:extension-manifest
Open

TrixNEW wants to merge 1 commit into
nvms:mainfrom
TrixNEW:extension-manifest

Conversation

@TrixNEW

@TrixNEW TrixNEW commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@TrixNEW

TrixNEW commented Sep 25, 2026

Copy link
Copy Markdown
Contributor Author

addresses #19 if u wanna do this differently lmk but i think it's fine realistically

Comment thread scripts/compat-manifest
elif loaded[key] != name:
errors.append("extension %s: zphp reports it as %s" % (name, loaded[key]))
for name in available.values():
expected = sorted(manifest["extensions"][name]["functions"], key=str.lower)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this comparison circular? expected comes from the manifest, while get_extension_funcs() gets its built in function list from extensions_generated.zig, which is generated from that same manifest.
This seems unable to catch a function being assigned to the wrong extension, should extension ownership also be checked against the reference php inventory?

This branch has not been deployed

No deployments
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.

2 participants