| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|\ |
|
| |\
| | |
| | | |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
By passing an array, you can add / delete URL in mass (bulk request)
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
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
|
| | |
|
| |
| |
| |
| | |
Fix #2062
|
| |
| |
| |
| |
| |
| |
| | |
Fix controller forward in WallabagRestController.
Update PHPDoc so it is sorted the same way as others one
Duplicate all annotations test to use both api & normal way
Also, make annotation tests independent to each other
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The generated error was “Unable to guess how to get a Doctrine instance from the request information.”.
I haven’t checked deeper in Doctrine (I know it was coming from the DoctrineParamConverter).
Anyway, I check for FosRest possiblity to add extra format without allowing them for every route (like it was done in the first place).
I finally found a way but it then seems all request goes to the FormatListener of FosRest so I needed to add a custom rules to match all request to be sure we don’t get a 406 error from FosRest.
Should be ok now …
|
|\ \
| |/
|/| |
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.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Instead of retrieve all informations about entries of a tag to just count them, we’ll count them before with a fastest query.
Also change the layout of the tag list in material design
|
|\ \
| | |
| | | |
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!)
|
| | |
|