Function names cannot contain dashes.

[REQUIRED] Environment info

firebase-tools: 7.6.0

Platform: Windows WSL 1

[REQUIRED] Test case

Provide a function name that contains a ‘-’ The emulator will error out with an error similar to:
Error: Function name “DriveActivity-getActivity” is invalid. Function names cannot contain dashes.

The function emulator does allow for ‘.’ in the name but those are invalid in function names.

[REQUIRED] Steps to reproduce

Create a function with a ‘-’ in the name.
run firebase functions:shell

[REQUIRED] Expected behavior

According to the Functions UI in the cloud console:

Name must start with a letter followed by up to 62 letters, numbers, or hyphens, and cannot end with a hyphen

[REQUIRED] Actual behavior

The function name errors out the functions emulator.
Error: Function name “DriveActivity-getActivity” is invalid. Function names cannot contain dashes.

[samtstern]

Ok I have sent out #1972 to address the confusion.

Here’s what’s going on (I asked someone who has been around Cloud Functions longer than I have):

• GCF allows - in function names, but we don’t in the Firebase CLI (explained below)
• When you group functions using exports.group = { functionA: ..., functionB: ... } we wanted to make the process intuitive and Javascript-y. So we use . notation to refer to those functions wherever possible. You do --deploy only:group.functionA, etc.
• Because . is not a valid name in a GCF function, when we deploy we replace the . with a - so that in the URL that function would be called group-functionA.
• In the functions:shell we wanted to reflect your code, so the function is defined as group.functionA. However the log message in functions:shell was showing the deployed name, which is wrong.

So I hope that makes sense! I do agree it’s confusing but changing this decision now would be hugely disruptive for a small benefit. So I hope that #1972 reduces confusion.

[tmk1991]

Still experiencing this firebase-tools 9.23.3