Skip to content

Support region configuration via FunctionsRegionToken is a BREAKING CHANGE #1945

Closed
@paulstelzer

Description

@paulstelzer

Today I wondered why my callable functions not working anymore. Then I saw that you tell "Support region configuration via FunctionsRegionToken". But if you not set it, the region is "null" and this region not exists.

So at the moment it is required to add { provide: FunctionsRegionToken, useValue: 'us-central1' }, to the providers section. From my point of view everyone who uses AngularFireFunctionsModule and callable functions, this is a BREAKING CHANGE

My feature request

it would be better, if no RegionToken is set, that the default value is 'us-central1'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions