When Netlify CMS uses the git-gateway backend, it will check for a
window.netlifyIdentity
object and use that to handle the whole auth flow.
This also sets defaults for the git-gateway endpoint, that means it
can be used in templates with zero configuration and fit with a
one-click deploy to Netlify approach.
Netlify Identity itself is based on our open-source GoTrue microservice,
and Netlify's Git Gateway project is completely open-source as well.
The git-gateway backend will work with Netlify without any setup, but can
also be configured to work with any selfhosted GoTrue and Git Gateway
instances.
Deletion was added in #485, but the function for the `test-repo` backend
was `deleteEntry` instead of `deleteFile` like it was supposed to be.
Also, setting the key for a deleted file to `undefined` did not really
remove that file from the object, so there were then errors stating
`file.content` is not defined. `delete`ing the "file" from the object
fixes this bug.
For example purposes, its helpful to allow users to run the test
backend without creating a repo object with nested objects for
each folder. This fix creates empty objects wherever needed.
* Files based collections skeleton
* listing file based cards
* create new entry with collection
* moved lookupEntry to main backend
* Editing single page Collections file
* List widget basic implementation
* Adjustments for test-repo
* check if value exists before trying to iterate over
