aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/Wallabag/ApiBundle
Commit message (Collapse)AuthorAgeFilesLines
* Use the article domain as author for export filesÉtienne Gilli2017-07-081-0/+1
| | | | | | | When exporting an entry, use the domain name as author name for epub, mobi and pdf formats, instead of 'wallabag'. Change the author from array to string, because for now, there is always only one author.
* CSJeremy Benoist2017-07-031-6/+6
|
* Fix PATCH methodJeremy Benoist2017-07-031-69/+142
| | | | | The PATCH method for the entry should only update what user sent to us and not the whole entry as it was before. Also, sending tags when patching an entry will now remove all current tags & assocatied new ones.
* Add a real configuration for CS-FixerJeremy Benoist2017-07-018-21/+21
|
* CSJérémy Benoist2017-06-281-2/+2
|
* Return null instead of falseJeremy Benoist2017-06-281-3/+27
|
* Avoid BC on exists endpointJeremy Benoist2017-06-231-2/+6
|
* Add client_credentials oAuth2 auth methodThomas Citharel2017-06-141-1/+1
| | | | Signed-off-by: Thomas Citharel <tcit@tcit.fr>
* CSJeremy Benoist2017-06-101-1/+1
|
* Few fixesJeremy Benoist2017-06-101-2/+2
|
* Add public filter/field in the APIJeremy Benoist2017-06-101-3/+24
| | | | | | Listing entries can now be filtered by “public”. Creating or patching an entry can now set is to public or remove the public. Entry response now include “is_public” boolean field
* Add ability to name the clientJeremy Benoist2017-06-081-3/+4
|
* Create a client when creating a user using the apiJeremy Benoist2017-06-072-5/+38
| | | | | | | | While creating a new user using the API, we also create a new client for the current user. So the app which just create the user can use its newly created client to configure the app. That new client is only return after creating the user. When calling the endpoint /api/user to get user information, the new client information won’t be return.
* Merge pull request #3181 from wallabag/api-content-patchJérémy Benoist2017-06-071-75/+75
|\ | | | | Add ability to patch an entry with more fields
| * Refactorize the way to save an Entry in the APIJeremy Benoist2017-06-071-102/+70
| |
| * Add ability to patch an entry with more fieldsJeremy Benoist2017-06-021-3/+35
| | | | | | | | | | | | | | | | | | Like when we create an entry, we can now patch an entry with new fields: - content - language - preview_picture - published_at - authors
* | Return 201 on user creationJeremy Benoist2017-06-021-5/+12
| |
* | Add translationJeremy Benoist2017-06-021-1/+1
| |
* | API user creation behing a toggleJeremy Benoist2017-06-021-3/+3
|/ | | | | | | | 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.
* Fix testsJeremy Benoist2017-06-011-22/+23
|
* Avoid returning objects passed by reference.Jerome Charaoui2017-06-011-2/+2
| | | | | | Objects are always passed by reference, so it doesn't make sense to return an object which is passed by reference as it will always be the same object. This change makes the code a bit more readable.
* Forced date can now be a timestamp tooJeremy Benoist2017-05-311-1/+1
| | | | Add adding more tests for forced content
* Improve docsJeremy Benoist2017-05-311-0/+3
|
* Use graby ContentExtractor to clean htmlJeremy Benoist2017-05-311-1/+0
| | | | It might be better to re-use some graby functionalities to clean html instead of building a new system.
* Add support for authorsJeremy Benoist2017-05-311-1/+5
|
* Allow other fields to be send using APIJeremy Benoist2017-05-311-15/+31
| | | | | | | | | | | | | | | | 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)
* Re-use `NewUserType` to validate registrationJeremy Benoist2017-05-301-39/+80
| | | | | | 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
* WIPThomas Citharel2017-05-292-0/+103
| | | | Signed-off-by: Thomas Citharel <tcit@tcit.fr>
* Move Tags assigner to a separate fileThomas Citharel2017-05-271-4/+4
| | | | Signed-off-by: Thomas Citharel <tcit@tcit.fr>
* Merge remote-tracking branch 'origin/master' into 2.3Jeremy Benoist2017-05-191-4/+13
|\
| * Merge pull request #3095 from aaa2000/api-error-on-fail-fetch-contentThomas Citharel2017-05-101-4/+13
| |\ | | | | | | Create a new entry via API even when its content can't be retrieved
| | * Create a new entry via API even when its content can't be retrievedadev2017-05-081-4/+13
| | | | | | | | | | | | Fix #2988
* | | Retrieve tag / tags value from query or requestJeremy Benoist2017-05-091-2/+2
| | | | | | | | | | | | | | | 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)
* | | Merge remote-tracking branch 'origin/master' into 2.3Jeremy Benoist2017-05-092-2/+7
|\| |
| * | Fix API pagination is broken if perPage is custom valueadev2017-05-081-1/+2
| |/ | | | | | | Fix #2720
| * Fix display the form errors correctlyadev2017-05-051-1/+5
| | | | | | | | | | | | | | | | | | Use `property_path` form option to map underscored form fields to object properties @see https://github.com/symfony/symfony/issues/9162#issuecomment-25431148 Fix #3067
* | Little refacto and send 400 on reaching urls limitJeremy Benoist2017-05-051-102/+94
| |
* | Added limitNicolas Lœuillet2017-05-011-0/+9
| |
* | Fix testsJeremy Benoist2017-05-011-1/+0
| |
* | Splitted the endpoint in twoNicolas Lœuillet2017-05-011-34/+62
| |
* | Added API endpoint to handle a list of URLNicolas Lœuillet2017-05-011-0/+71
| | | | | | | | By passing an array, you can add / delete URL in mass (bulk request)
* | Fix testsJeremy Benoist2017-04-291-2/+0
| |
* | Added endpoint to handle URL list to add/delete tagsNicolas Lœuillet2017-04-242-26/+63
| |
* | Added API endpoint to handle a list of URL and to add/delete tagsNicolas Lœuillet2017-04-241-0/+68
| |
* | return id of article instead of true if entry existsThomas Citharel2017-02-241-2/+2
|/
* Be consistent between migration & schema definitionJeremy Benoist2016-12-191-1/+1
|
* Fix tests & deprecation noticeJeremy Benoist2016-12-152-1/+1
|
* Return 304 when content isn't reloaded using the APIJeremy Benoist2016-11-221-3/+3
| | | | | | 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.
* Return an explicit error if reload failJeremy Benoist2016-11-201-6/+3
|
* Fixing testsJeremy Benoist2016-11-201-1/+1
|