| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
I've added a toggle feature (in internal settings) so that user api creation can be disabled while form registration still can be enabled.
Also, the /api/user endpoint shouldn't require authentication. Even if we check the authentication when sending a GET request, to retrieve current user information.
I've moved all the internal settings definition to config to avoid duplicated place to define them.
I don't know why we didn't did that earlier.
|
|\
| |
| | |
Isolated tests
|
| |
| |
| |
| | |
Use https://github.com/dmaicher/doctrine-test-bundle to have test isolation.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Entry API can now have these new fields:
- content
- language
- preview_picture
- published_at
Re-use the ContentProxy to be able to do the same using the web UI (in the future).
htmLawed is used to clean stuff from content, I hope it’ll be enough to avoid security breach.
Lower content validation when we want to update an entry with content already defined. Before, language & content_type were required. If there weren’t provided, we re-fetched the content using graby. I think these fields aren’t required for an entry to be created. So I removed them.
Which means some import from the v1 export won’t be re-fetched since they provide content, url & title.
Also, remove liberation link from Readability import to avoid overlaping import (from wallabag v1, which had the same link)
|
| |
|
|
|
|
|
|
| |
The only ugly things is how we handle error by generating the view and then parse the content to retrieve all errors…
Fix exposition fields in User entity
|
|\ |
|
| |\
| | |
| | | |
Create a new entry via API even when its content can't be retrieved
|
| | | |
|
| | |
| | |
| | |
| | | |
Fix #2988
|
| | |
| | |
| | |
| | |
| | | |
It allows to request to delete a tag using query string instead of body parameter (which seems to be the standard).
Instead of breaking the previous behavior, I used a generic way to retrieve parameter (which looks into request attributes, query parameters and request parameters)
|
|\| | |
|
| |/
| |
| |
| | |
Fix #2720
|
| | |
|
|\ \
| | |
| | | |
Added API endpoint to handle a list of URL
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
By passing an array, you can add / delete URL in mass (bulk request)
|
|\ \ \
| |/ /
|/| | |
Added notmatches operator for tagging rule
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
|
| |
Previously it was a 400 but this is more related to a real error.
Using the API user should only know the content got reloaded or not.
If reloaded: 200 otherwise: 304.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Fix #2503
|
| | |
|
|\ \
| |/
|/| |
API: ability to export entry in all available format (epub, pdf, etc...)
|
| |
| |
| |
| |
| | |
Export isn't available for json & xml because user can use the default
entry endpoint instead.
|
|\ \
| | |
| | | |
Changed relation between API client and refresh token
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we remove the client, we should ensure that access_token are also removed.
To ensure that, I created a test that generated an access_token. So when we remove the client, this association should be cascaded and shouldn’t generate an error.
Also I moved some Api related stuff to the ApiBundle (like the developer controler and ClientType form)
|
|\ \ \
| | | |
| | | | |
Ability to check multiple urls in API
|
| | |/
| |/| |
|
|/ /
| |
| |
| |
| |
| | |
When the association between a tag and an entry is removed, if the tag doesn’t have other entries, we can remove it.
Also add more tests for that part and ensure TagControllerTest is isolated from the rest of the test suite (finally!)
|
|/ |
|
|
|
|
| |
We forgot to pass them to the factory
|
| |
|
|
|
|
| |
It should allow third party to check if an url was already saved by a user
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Also, retrieve tag from the request instead of the query (which will be the same but it's more easy to test).
Moved down `deleteTagAction` because it conflicted with the new action:
api_delete_tag => /api/tags/{tag}.{_format}
api_delete_tags_label => /api/tags/label.{_format}
And finally, throw exception when a tag is not found before removing it.
|
| |
|