jackmahoney / emaile2e-javascript-client Goto Github PK

I am creating many inboxes in my tests, saving their IDs, then destroying them in a loop at the very end of the test suite. When I do this, all of the DELETE requests fail. Are the inboxes automatically removed after some time?

Here is the response error I am getting so you can check your logs:

timestamp":"2018-02-15T01:05:27.487+0000","status":500,"error":"Internal Server Error","message":"No EntityManager with actual transaction available for current thread - cannot reliably process \'remove\' call","path":"/inboxes/3d3be8ed-3cbe-4520-b6e0-29e4da928678

Thanks for the great service!

I noticed that it seems a bit slow to receive emails (sometimes 20 seconds). This might be out of your control, but I tested my same application code with this service and the emails were delivered there almost instantly. https://putsbox.com/

Although the emails are delivered, the "from" field in my case looks like this,

01000161951a5c59-bcc4b5b3-a421-47da-aae1-5e3b360ddbef-000000@amazonses.com

when it should have been,

[email protected]

When I tried using mailgun, the "from" field in the result looked like,

[email protected]

I think there is something wrong with the way the inboxes are setup, that is causing the email to be delayed and with the wrong "from" field.

Are you planning to charge for this service? If it was open source I would be happy to contribute.

In your recent versions:
let payload = await slurp.createRandomInboxUsingPOST(MAILSLURP_API_KEY)

fails with:
TypeError: Cannot read property 'type' of undefined
at node_modules/mailslurp-client/src/ApiClient.js:297:20

Due to:
return this.apiClient.callApi( '/inboxes', 'POST', pathParams, queryParams, headerParams, formParams, postBody, authNames, contentTypes, accepts, returnType )
vs function definition:
function callApi(path, httpMethod, pathParams, queryParams, collectionQueryParams, headerParams, formParams, bodyParam, authNames, contentTypes, accepts, returnType)

It treats contentTypes (['application/json']) as authNames, so it fails. The api call must not have been updated to work with the new function definition?