search

advanced-rest-client / arc-electron

Advanced REST Client - Desktop application
Other
1.41k stars 225 forks source link

ARC Ruined Saved APIs after Update #114

Closed cnrabdullah closed 5 years ago

cnrabdullah commented 5 years ago

After updating to this version, we imported our projects back again and then realized that the Method selection was cleared in all requests. We reverted them one by one by comparing with the JSON files. Then we realized that it also changed all of our URLs to lower cases. It ruined all of our requests, we had serious problems with our customers.

Expected outcome

What should happen?

Actual outcome

What happened?

Versions

App: 12.1.4 Platform: win32 Electron: 2.0.2 Chrome: 61.0.3163.100 V8: 6.1.534.41 Node: 8.9.3

Steps to reproduce

jarrodek commented 5 years ago

Hi, Thank you for issue report. There was no updates for months. Did you move the data from Chrome apps to this app? Could you share a part of the data you have in the export file (without customer data of course, fust to be able to reproduce).

cnrabdullah commented 5 years ago

Hi,

Thanks for the reply.

As I said there are two situations:

  1. The method selections of the request are empty when I load a request even the ARC knows the method (I can see the method when I open the details tab or I can see it in the project tab too). See attached file (1_method_selection.JPG). It makes me select the method for each loaded file one by one than save&export the project again.
  2. The second problem is the ARC changed all of our URLs to lower case. We moved from the Chrome app to the desktop app version, it might be the reason but I'm not sure if it is exactly related to this. I have either not come up this issue before moving to the desktop version or it is exactly related to moving to the desktop version. I have a hint for you about this issue. We have 2 backup exports of the same project, one is taken at 22-10-2018 and the other one is taken at 27-10-2018. When I open them in notepad++, I can see that the lower case issue happened at the export which was taken at 27-10-2018 but the 22-10-2018 backup is okay. So the problem might have happened between these dates. I'm not sure if I updated the ARC as soon as the update arrived.

I can see the versions of the arc at the exports like below:

If you want, I can send you one part of our exports.

Regards, Abdullah.

Paweł Psztyć notifications@github.com, 24 Oca 2019 Per, 05:35 tarihinde şunu yazdı:

Hi, Thank you for issue report. There was no updates for months. Did you move the data from Chrome apps to this app? Could you share a part of the data you have in the export file (without customer data of course, fust to be able to reproduce).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/advanced-rest-client/arc-electron/issues/114#issuecomment-457044322, or mute the thread https://github.com/notifications/unsubscribe-auth/AOG4vEOw1q2N1WEg3fHbr_QzFK5gqLuUks5vGRv3gaJpZM4aKW2g .

-- Abdullah Çınar Elektronik ve Haberleşme Mühendisliği Bölümü Kocaeli Üniversitesi, 41380, Kocaeli, Türkiye.

jarrodek commented 5 years ago

Thank you for the response. I take data import/export very seriously. I can't see the image attached to the email (GitHub apparently can't process them).

Version 10.x is only available in Chrome Web Store and because of Google's decision to terminate support for Chrome apps I need to move to native platform. You are using desktop client (version 12.x) and apparently there is an issue in the export module. Tomorrow morning I'll investigate this issue.

I almost finished release of the next version where this issue will be fixed. I'm still writing tests for changed code so i will take a look into import/export tests to check if there's any problem with case sensitivity.

jarrodek commented 5 years ago

I cannot reproduce the issue. Can you please describe the steps so I can help? From which version to which version data move has issues with case sensitivity? Is this URL issue only?

jarrodek commented 5 years ago

This should be fixed in 13.0.0 as the import logic was updated and well tested. I cannot reproduce this issue anymore.