Chris-pulse-stripe-mock-wipe

[thin swallow]

Hello 👋

[glass osprey]

➜ ~ stripe-mock
stripe-mock master
Routing to 265 path(s) and 424 endpoint(s) with 424 validator(s)
Listening for HTTP at address: [::]:12111
Listening for HTTPS at address: [::]:12112
Request: GET /v1/payment_intents/search
Request data = map[query:metadata["invoice_future"]:"5"]
Response: elapsed=727.677µs status=200

[thin swallow]

Give me a moment to catch up here 🙂

[glass osprey]

stripe-mock seems to be "retaining" old data

this is me starting stripe-mock, and then querying, and it finding data

this is because I previously stored data in stripe-mock, but it was bad data, so I need to "wipe" stripe-mock

[thin swallow]

hmm not seeing a straight forward way to get this done
let me ask a colleague

Can you provide more information on how you were storing the data in stripe-mock?
We'd like to see if we can reproduce this

[glass osprey]

that's complicated to answer, but the real question is: if I start stripe-mock, why does querying for metadata return results?

            $results = $stripe->charges->search(['query' => 'metadata["invoice_future"]:' . $invoiceFuture->id. '"'], config('account.stripe_options'));
            dd($results->data[0]);

1. bash run stripe-mock
2. run a search query for metadata
3. results found
   how are results found on freshly started stripe-mock?

[thin swallow]

I'm not sure

@glass osprey This may need more time to debug. can you write in to our support with as many as details that you can provide?
https://support.stripe.com/contact/email

[glass osprey]

yup, will do

thanks for the help!

[thin swallow]

NP! Appreciate your patience 🙂