Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API bugs related to description #29

Open
erykwarren opened this issue Mar 9, 2017 · 8 comments
Open

API bugs related to description #29

erykwarren opened this issue Mar 9, 2017 · 8 comments
Assignees

Comments

@erykwarren
Copy link
Owner

erykwarren commented Mar 9, 2017

No description provided.

@erykwarren erykwarren self-assigned this Mar 9, 2017
@erykwarren
Copy link
Owner Author

@eryk Warren Could you please list API bugs related to description sorted by priority. You can do that in comments or you can attach Google Doc with a list.

@erykwarren
Copy link
Owner Author

➤ Eryk Warren commented:
@alexander Belyaev Here is the ordered list. I put the zendesk reference number, when available. I believe I have one zendesk reference missing (Multiple description formats...).

The one called "Long delay..." is about the post-processing formatting of the description. It would be great to have the API return the exact final description when creating/updating a task instead of finding out about it at a later time.

Let me know if you have any question regarding these.


253626 API Rate Limit needs to be by Oauth account
245878 API: Hyperlink duplicated in description
Long delay when updating description
Multiple description formats lost when creating tasks through API
244255 <ol> transformed into <ul>
244334 Lists entered in UI don't report properly in API
238976 Tables are badly supported in descriptions

@erykwarren
Copy link
Owner Author

@eryk Warren On 245878 - it's only about "mailto:" links, is that correct?

@erykwarren
Copy link
Owner Author

➤ Eryk Warren commented:
in fact, no, we've seen the same problem with regular http links.

@erykwarren
Copy link
Owner Author

@eryk Warren Is it consistent and always reproduces with "mailto:" links? And is it completely random with regular links, no patterns we could try to reproduce?

@erykwarren
Copy link
Owner Author

➤ Eryk Warren commented:
@alexander Belyaev The double link bug is very easy to reproduce. Here are the steps:

@erykwarren
Copy link
Owner Author

➤ Eryk Warren commented:
curl -X POST -H "Authorization: bearer KXrOLp9tUKqI1BTeCEIXyCloAI5Envz7OSSn4zx3rTMUtb6gUntghnoqPA1GtHL0-N-N" -H "Content-Type: application/x-www-form-urlencoded" -d 'title=Double link&description=<a href="https://google.com&#34;https://google.com&#34;https://google.com&#39;; https://www.wrike.com/api/v3/folders/IEAA2I3II4CKBQYH/tasks

The data you receive from this command includes:

"id": "IEAA2I3IKQCT3CGN",
"description": "<a href=&#34;https://google.com\&#34;; rel=&#34;nofollow&#34;>";,

However, after a few minutes, a query to that specific task returns:

curl -X GET -H "Authorization: bearer KXrOLp9tUKqI1BTeCEIXyCloAI5Envz7OSSn4zx3rTMUtb6gUntghnoqPA1GtHL0-N-N" https://www.wrike.com/api/v3/tasks/IEAA2I3IKQCT3CGN

"description": "<a href=&#34;https://google.com\&#34;; rel=&#34;nofollow&#34;></a><a href=&#34;https://google.com\&#34;; rel=&#34;nofollow&#34;>

@erykwarren
Copy link
Owner Author

➤ Eryk Warren commented:
I'll add these instructions to the Zendesk ticket.

@erykwarren erykwarren modified the milestone: Milestone 1 Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant