Skip to content

Conversation

@mbleigh
Copy link
Contributor

@mbleigh mbleigh commented Aug 2, 2021

As per review in other branch.

inlined and others added 19 commits July 14, 2021 13:08
The actual encoding/decoding/error logic etc. of callable functions
will stay the same between v1 and v2, so they should be in a /common
file.

The rest of /v1 is about trigger options, cors, etc.

onCall's CORS options are part of the v1 namespace because v2 adds
a "cors" option to HttpsOptions. In the v2 API, we will default
to `"cors": true`, but a customer could say `"cors": "my.firebase.app"`
and we will respsect it.

I wish there was a way to make this diff not so noisy. Most of this
is cut & paste.
Builds upon #915

Creates the first bits of v2/

setGlobalOptions allows customers to set options that will be preserved
across any function written in the v2 API.

v2/https has webhook and callable function support. In addition to
previous features, customers can now specifiy `cors` as a shorthand for
using CORS middleware.

We will probably eventually support scheduled functions in the HTTPS
namespace but that will have to wait for another day.
Copy link
Member

@inlined inlined left a comment

Choose a reason for hiding this comment

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

Looks like there's some crazy diffs going on here, but as long as it merges cleanly, LGTM

@mbleigh mbleigh changed the base branch from master to inlined.v2-http August 4, 2021 15:42
@mbleigh mbleigh changed the base branch from inlined.v2-http to master August 4, 2021 15:43
@mbleigh mbleigh merged commit 6d16d52 into master Aug 4, 2021
@mbleigh mbleigh deleted the mb-params branch August 4, 2021 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants