| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Also, do not run the hashed_url migration into a Doctrine migration
|
|
|
|
|
|
| |
- Add migration
- Use md5 instead of sha512 (we don't need security here, just a hash)
- Update tests
|
|
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The expect parameter enables an application to request the whole entry
or only the id when requesting its deletion.
`expects` defaults to `entry` to prevent any API breakage.
Fixes #3711
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| | |
|
| |
| |
| |
| | |
And run newer cs fixer
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
- Adds a new `search` key to `src/Wallabag/ApiBundle/Resources/config/routing_rest.yml`
- Reuses the `getBuilderForSearchByUser` method from the EntryRepository
- Supports, `term`, `page`, and `perPage` query parameters
- Some very basic tests
|
| |
| |
| |
| |
| |
| |
| | |
Useful for api client which required some information.
We might add more inside them in the future.
The endpoint /api/version should be avoided now as it contains not so much information rather the version.
|
|\| |
|
| |
| |
| |
| | |
Only allowed parameter are asc & desc
|
| |
| |
| |
| |
| |
| |
| |
| | |
the user
Fixes #3815
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| |
| |
| |
| |
| |
| |
| | |
Thanks to the BC compatibility, almost nothing have to be changed.
All changes are related to new bundle version of:
- SensioFrameworkExtraBundle
- DoctrineFixturesBundle
|
| | |
|
|/ |
|
|
|
|
| |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
|
| |
Workaround for https://github.com/wallabag/android-app/issues/646
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
|
|
|
|
|
| |
Add a new helper to set a default title when it's empty:
1/ use basename part of entry's path, if any
2/ or use domain name
Fixes #2053
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
| |
I didn't try to find which package introduced a BC (might be user-bundle
or jms serializer)
|
|
|
|
| |
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
|
|
|
|
|
| |
migration
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| |
|
| |
|
|
|
|
| |
Also update tests urls
|
|
|
|
|
|
|
|
| |
This date is used to sort starred entries.
Can not use Entry::timestamps method otherwise starred_at will be updated each time entry is updated.
Add an updateStar method into Entry class
A migration script has been added in order to set starred_at field.
|
| |
|
|\
| |
| | |
Use the article publisher as author for exported files
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| |
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Add ability to patch an entry with more fields
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Like when we create an entry, we can now patch an entry with new fields:
- content
- language
- preview_picture
- published_at
- authors
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
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.
|
| |
|