Skip to content

fix: align faas runner detection with protocol and validate runners#105

Open
Ishita-190 wants to merge 3 commits intometacall:masterfrom
Ishita-190:ishi
Open

fix: align faas runner detection with protocol and validate runners#105
Ishita-190 wants to merge 3 commits intometacall:masterfrom
Ishita-190:ishi

Conversation

@Ishita-190
Copy link

@Ishita-190 Ishita-190 commented Feb 26, 2026

Summary

Changes made to centralize runner metadata, improve type safety, and add validation for multipart runner inputs while keeping behavior consistent with protocol.

Related issue

#104
and metacall/protocol#41

Type of change

  • Bug fix
  • New feature
  • Documentation
  • Chore / CI
  • Breaking change

How to test

Steps to reproduce or verify the change locally:

  1. Checkout the branch
  2. Run npm ci (or equivalent)
  3. Run npm test and any additional verification steps
image

Checklist

  • I have read the contributing guidelines
  • I added tests that prove my fix is effective or that my feature works
  • [] I updated documentation if necessary

for (const [runner, deps] of Object.entries(runnerDeps)) {
const command = installCommand[runner];
for (const runner of resource.runners) {
const command = Runners[runner].installCommand;
Copy link
Contributor

Choose a reason for hiding this comment

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

These are the correct installCommand.

python: 'metacall pip3 install -r requirements.txt',
nodejs: 'metacall npm i',
ruby: 'metacall bundle install',
csharp: 'metacall dotnet restore && metacall dotnet release'

But, i don't see metacall prefix in the protocol.
https://github.com/metacall/protocol/blob/master/src/language.ts#L21

Also, csharp installCommand is incomplete.
https://github.com/metacall/protocol/blob/master/src/language.ts#L47

Any reason you skipped metacall ?

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