b25da62cca
no issue - the model & api layer suffered from missing fields when creating resources - usually there is only a handful of fields which are required to insert a resource - the other fields are nullable and/or get defaults assigned - the API only returned the configured default fields and the fields you have sent to the API - this resulted in a response with missing fields - if you have listend on "created" event, the same happend - you received a model with missing fields - we now set the undefined fields to null on purpose to ensure a full model for both cases @NOTE: There is no endpoint to serve webhooks (not for v0.1, not for v2). Exposing the secret is required if an integration fetches it's api keys and it's webhooks. The secret is currently un-used and not implemented. |
||
|---|---|---|
| .. | ||
| old | ||
| README.md | ||
Acceptance Tests
This folder should only contain a set of basic API use cases.
We are currently refactoring the test env. The "old" folder currently contains all API tests for the stable API version (v2). The goal is:
- either keep a test if it's a basic use case e.g. upload an image, schedule a post, download a theme
- otherwise move the test to regression api v2 tests
We probably need a differentiation for the acceptance tests for session and api_key authentication.
Before we move tests:
- we have to re-work how are test utility is structured
- we have to reduce tests