| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
If we keep the `0` value, the card might be inserted in the middle of the
list, making it hard to find it later on.
Always append the card at the end of the list by setting a sort value
based on the number of cards in the list.
|
|
|
|
| |
This has the side effect of always inserting the element at the end.
|
|
|
|
|
|
|
|
|
| |
When moving around the swimlanes or the lists, if one element has a sort
with a null value, the computation of the new sort value is aborted,
meaning that there are glitches in the UI.
This happens on the first swimlane created with the new board, or when
a swimlane or a list gets added through the API.
|
|
|
|
| |
fixes #1688
|
| |
|
|
|
|
|
| |
Still need to create the swimlane right after the one that has been
created
|
|
|
|
|
|
|
| |
This allows to use the header as a separator between swimlanes.
This will be most useful when we can set the background color of these
headers.
|
| |
|
|
|
|
|
|
|
|
|
| |
To unset the color through the IFTTT, we need a white entry.
However, we do not want to show the white enry in the hamburger
`Set Color` entry.
We can also give the `white` capability to the API, it won't hurt
and be more straightforward.
|
| |
|
| |
|
|
|
|
|
| |
This allows to show checks on the color with the correct color instead
of plain white.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix: Translate and add colors to IFTTT Rules dropdown."
|
| |
| |
| |
| |
| |
| |
| | |
This fixes commit 44e4df2492b95226f1297e7f556d61b1afaab714.
When the label has a name, not setting `translatedname` results in a
blank item in the IFTTT label trigger.
|
|/ |
|
|\
| |
| | |
Allow to call export from the API
|
|/
|
|
|
|
|
|
|
| |
This allows to retrieve the full export of the board from the API.
When the board is big, retrieving individual cards is heavy for both
the server and the number of requests.
Allowing the API to directly call on export and then treat the data
makes the whole process smoother.
|
|
|
|
| |
Thanks to xet7 !
|
|\
| |
| | |
Set the card color with the color picker
|
|/
|
|
| |
When triggered from the hamburger
|
| |
|
|\
| |
| | |
Add per card color
|
| | |
|
| |
| |
| |
| |
| |
| | |
Currently only dropdown, no palette
Fixes: #428
|
| |
| |
| |
| | |
Currently the only way to set it is via the REST API
|
|/ |
|
|
|
|
|
|
| |
Thanks to Chartman123 !
Closes #2114
|
| |
|
|
|
|
|
|
| |
Docs](https://github.com/wekan/wekan/pull/1965).
Thanks to bentiss.
|
|\ |
|
|/| |
|
| |
| |
| |
| |
| | |
Same for snap: embed the documentation of the REST API
in the snap.
|
| |
| |
| |
| |
| |
| | |
Aligning with the requirement to run the container without
external resources: embed the documentation of the REST API
directly in the Docker image.
|
| |
| |
| |
| |
| | |
Same thing than in the Dockerfile, snaps need
to embed the current openapi yaml file.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When pulling the docker container snapcore/snapcraft
to build the snap, those 2 packages are not present
by default leading to a failure in the snap creation.
Note: it is good to call `apt-get update` before
`snapcraft` or the build will fail.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is common to use Ubuntu 16.04 to build snaps. For example,
the official docker container to build snaps is using this old
distribution.
However, Ubuntu 16.04 ships Python 3.5.X which is not compatible
with the f-strings in generate_openapi.py. This is sad, because
we need to use the `.format()` syntax to make it compatible.
|
| |
| |
| |
| |
| |
| | |
When we build the docker container, we need to generate the openapi
description in it so the geenrated API actually matches the code
the container is running.
|
| |
| |
| |
| | |
So we can have a decent REST API documentation generated.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The API is generated by a custom script that parses the models directory.
Once the API is generated, tools like https://editor.swagger.io/ or
Python bravado can parse the file and generate a language friendly API.
Note that the tool generate an OpenAPI 2.0 version because bravado
doesn't handle OpenAPI 3.0.
The script also parses the JSDoc with a custom parser to allow
customization of the description of the fields.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f61942e5cb672d3e0fd4df6c5ff9b3f15f7cb778.
Adding a member is actually already handled by
POST', '/api/boards/:boardId/members/:userId/add'
So this function is purely duplicated.
Not to mention that the '/add' one allows to set permissions
so this one in this commit is less interesting.
|
| |
| |
| |
| | |
Thanks to ajRiverav !
|
|\ \
| | |
| | | |
update license to year 2019
|
| | | |
|
| |/
|/| |
|
|/ |
|
|
|
|
|
|
| |
Thanks to xorander00 !
Closes #2101
|