Comments (5)
thorsten-stripe
commented on June 8, 2024
2
Thanks @laurenzlong, this is because collections can only be either at the root or within a document, correct? So for stripe/customers/invoices, stripe is the root collection, customers is a document, invoices is a sub-collection of the customers document. Is that correct?
So using stripe/products for products path and stripe/customers for customer path is impossible, but using stripe/mysubsapp/products for products path and stripe/mysubsapp/customers for customer path would be possible. Would that be an antipattern though?
I'll add the validationRegex π
from stripe-firebase-extensions.
laurenzlong
commented on June 8, 2024
2
And having a more nested collection path like stripe/mysubsapp/customers is
not an antipattern.
β¦On Wed, Aug 5, 2020, 7:16 PM Lauren Long ***@***.***> wrote:
Yep, that's right!
On Wed, Aug 5, 2020, 12:08 PM Thor ι·η₯ ***@***.***> wrote:
> Thanks @laurenzlong <https://github.com/laurenzlong>, this is because
> collections can only be either at the root or within a document, correct?
> So for stripe/customers/invoices, stripe is the root collection,
> customers is a document, invoices is a sub-collection of the customers
> document. Is that correct?
>
> So using stripe/products for products path and stripe/customers for
> customer path is impossible, but using stripe/mysubsapp/products for
> products path and stripe/mysubsapp/customers for customer path would be
> possible. Would that be an antipattern though?
>
> I'll add the validationRegex π
>
> β
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#28 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AA6OKFG4R6S26KV2ITE2MD3R7GU25ANCNFSM4PVJL2XQ>
> .
>
from stripe-firebase-extensions.
laurenzlong
commented on June 8, 2024
1
Firestore collections need to be an odd number of segments (i.e. customers or stripe/customers/invoices). I recommend adding the regex ^[^/]+(/[^/]+/[^/]+)*$ to all the Firestore collection path parameters in both extensions.
from stripe-firebase-extensions.
thorsten-stripe
commented on June 8, 2024
I was able to reproduce this on my account:
; RESOURCE_ERROR at /deployments/firebase-ext-firestore-stripe-subscriptions/resources/createCheckoutSession: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":{"code":400,"message":"The request has errors","status":"INVALID_ARGUMENT","details":[{"@type":"type.googleapis.com/google.rpc.BadRequest","fieldViolations":[{"field":"event_trigger","description":"Expected value stripe/customers/{uid}/checkout_sessions/{id} to match regular expression [^/]+/[^/]+(/[^/]+/[^/]+)*"}]}],"statusMessage":"Bad Request","requestPath":"https://cloudfunctions.googleapis.com/v1/projects/stripe-subscriptions-firebase/locations/us-central1/functions","httpMethod":"POST"}}; RESOURCE_ERROR at /deployments/firebase-ext-firestore-stripe-subscriptions/resources/onCustomerDataDeleted: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":{"code":400,"message":"The request has errors","status":"INVALID_ARGUMENT","details":[{"@type":"type.googleapis.com/google.rpc.BadRequest","fieldViolations":[{"field":"event_trigger","description":"Expected value stripe/customers/{uid} to match regular expression [^/]+/[^/]+(/[^/]+/[^/]+)*"}]}],"statusMessage":"Bad Request","requestPath":"https://cloudfunctions.googleapis.com/v1/projects/stripe-subscriptions-firebase/locations/us-central1/functions","httpMethod":"POST"}}@jhuleatt @laurenzlong any idea what's happening here? Are paths supported in the extension.yaml file? Do I need to specify a validationRegex like here: https://github.com/firebase/extensions/blob/master/firestore-translate-text/extension.yaml#L110?
from stripe-firebase-extensions.
laurenzlong
commented on June 8, 2024
Yep, that's right!
β¦On Wed, Aug 5, 2020, 12:08 PM Thor ι·η₯ ***@***.***> wrote:
Thanks @laurenzlong <https://github.com/laurenzlong>, this is because
collections can only be either at the root or within a document, correct?
So for stripe/customers/invoices, stripe is the root collection, customers
is a document, invoices is a sub-collection of the customers document. Is
that correct?
So using stripe/products for products path and stripe/customers for
customer path is impossible, but using stripe/mysubsapp/products for
products path and stripe/mysubsapp/customers for customer path would be
possible. Would that be an antipattern though?
I'll add the validationRegex π
β
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6OKFG4R6S26KV2ITE2MD3R7GU25ANCNFSM4PVJL2XQ>
.
from stripe-firebase-extensions.
Related Issues (20)
- Update to node 18 or 20 -> Node 14 will be deprecated on january 31 HOT 12
- Webhook handler for Stripe event failed: User not found! HOT 6
- createCustomer is not triggered
- createPortalLink success_url HOT 1
- success_url and cancel_url not working in mobile
- CustomClaims "stripeRole" is removed on overdue subscriptions.
- Firebase stripe extension Error creating secrets HOT 5
- Upgrade Cloud Functions to v2 (Gen2) HOT 4
- Support trial βΒ there's no longer the legacy option for setting a trial in Stripe HOT 2
- Dragon
- Dragon
- Webhook handler not updating cancellation details on Firebase. HOT 4
- cancel/resume/update subscriptions directly from firestore-stripe-payments
- Interacting with subscriptions in firestore-stripe-web-sdk
- Error installing HOT 1
- Extension requires deprecated feature of Stripe to support free trials for subscriptions HOT 4
- Embedded Payment Form
- Error: No such customer: 'cus_....' HOT 1
- extension double-charging customers for old invoices?!
- getStripePayments -> ERROR FirebaseError: Expected first argument to collection() to be a CollectionReference, a DocumentReference or FirebaseFirestore HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stripe-firebase-extensions.