The problem of the API adding interface

[krestyanikov]

Hello,

I noticed the strange interface behavior when adding a new API

1. I cannot save the API until it was successfully tested. This is not always convenient, sometimes you need to save the API as a template.
2. I cannot create a copy of the already created API. This is a problem if there are many similar APIs, in this case I need to create it manually every time
3. The API is completely cleaned if I click on the empty area in the API list. I clicked by accident and lost all my results

result

4. The remote parameter is displayed. There is no way to remove the parameter did not remove the line

5. Switching type of request does not give a result, it seems to me that it is always GET

6. I can’t form BASE64 TOKEN for BASIC AUTH. This is a fairly common operation. It would be good to have such an option

Is it possible to improve user experience when connecting the API? Thank you!

[thagikura]

Hi,

Thanks for your feedback!
All the points you mentioned seem reasonable. I'll keep them in mind as future improvements/fixes.

Thanks!

[thagikura]

0.7.8.1 version fixes those above.

I think I couldn't reproduce 4th point about the parameter (or I got it wrong).
If these still persist, please let me know.

Thanks!

[krestyanikov]

Hello Takeshi Hagikura

After I performed the ComposeFlow update my version is 0.7.8.0

1. Is Ok
2. Is Ok. Perfect!
3. This problem is still relevant. Data is erased when clicking on the API list item.
4. This is fixed!
5. This is fixed!
6. Is Ok. Perfect!

I was finally able to advance in testing authorization. However, I noticed the following problems

7. I cannot change the created parameter. I wanted to add a default value to the parameter and could not do this. As a result, I deleted it and created the parameter again, it is not very convenient

8. I noticed that in some places of the Composeflow interface, I cannot select and copy the text. This is especially inconvenient for an API preview. I wanted to copy the resulting token to use it to test another API, but could not do it. As a result, I added token by typing it on the keyboard

9. For a long time I could not understand how I could add Bearer to the authorization token. Suppose I retained Access_token in State, but I can’t change it and add to the beginning of the Bearer token to convey it to the Authorization Header. I did not find such an action for Workflow. It would be logical to have something like a concatenation

10. Alas, I received an ApiResult error when starting the project. It seems to be due to the fact that I can’t choose a JSON parameter for SetState

Thank you!