Warning about using `.value()` whenever an expression is used in the `cors` option

[segevfiner]

Related issues

[REQUIRED] Version info

node: 22.17.1

firebase-functions: 6.4.0

firebase-tools: 14.11.1

firebase-admin: 13.4.0

[REQUIRED] Test case

import { onCall } from 'firebase-functions/v2/https';
import { projectID } from 'firebase-functions/params';

export const helloworld = onCall<unknown, string>(
  { cors: projectID.equals('something').thenElse(['http://localhost:5173'], []) },
  () => {
    return 'Hello from Firebase!';
  },
);

[REQUIRED] Steps to reproduce

1. Just create a firebase-functions project and deploy the given function.

[REQUIRED] Expected behavior

Deploys cleanly without warnings.

[REQUIRED] Actual behavior

Gets a warning:

{"severity":"WARNING","message":"params.PROJECT_ID == \"something\" ? [\"http://localhost:5173\"] : [].value() invoked during function deployment, instead of during runtime."}
{"severity":"WARNING","message":"This is usually a mistake. In configs, use Params directly without calling .value()."}

{"severity":"WARNING","message":"example: { memory: memoryParam } not { memory: memoryParam.value() }"}

Despite not using .value() in my code. The .value() is inside firebase-functions own code.

Were you able to successfully deploy your functions?

Yes.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[CorieW]

Hi @segevfiner

Thanks for reporting this issue! We’ve received it and are reviewing it. We’ll provide updates as soon as possible.