"Components" sidebar section take a while to load #3850

[vrubezhny]

Fixes: #3850
Depends on: #4467

Signed-off-by: Victor Rubezhny [email protected]

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 85.18519% with 12 lines in your changes missing coverage. Please review.

Project coverage is 43.84%. Comparing base (da60441) to head (9f8055f).
Report is 573 commits behind head on main.

Files with missing lines	Patch %	Lines
src/odo/odoPreference.ts	89.85%	7 Missing ⚠️
src/registriesView.ts	16.66%	5 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #4473       +/-   ##
===========================================
+ Coverage   32.37%   43.84%   +11.47%     
===========================================
  Files          85       99       +14     
  Lines        6505     8060     +1555     
  Branches     1349     1691      +342     
===========================================
+ Hits         2106     3534     +1428     
- Misses       4399     4526      +127     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vrubezhny]

This PR depends on #4467

[datho7561]

If I add a new registry (eg. https://registry.stage.devfile.io) it appears in the sidebar. However, when I open the Devfile browser, the new Devfiles aren't shown. If I manually hit the refresh button and reopen the Devfile browser, then it seems to work.

If there is an error in the registry URL (eg. I use http instead of https or I misspell some part of the URL), there is an error in the logs, but no notification pops up to tell me that it failed. The only way I can tell that it failed is that there is nothing new in the sidebar.

[vrubezhny]

If I add a new registry (eg. https://registry.stage.devfile.io) it appears in the sidebar. However, when I open the Devfile browser, the new Devfiles aren't shown. If I manually hit the refresh button and reopen the Devfile browser, then it seems to work.

This is for #4467 as this PR only removes the usages of odo preference ...-like command usages.
A believe it's fixed now in #4467. There is still an issue with adding a registry when the Devfile Editor is already opened, but, imho, it's not about the changes made in #4467 nor in this PR - to be fixed later.

If there is an error in the registry URL (eg. I use http instead of https or I misspell some part of the URL), there is an error in the logs, but no notification pops up to tell me that it failed. The only way I can tell that it failed is that there is nothing new in the sidebar.

Fixed in #4467

[vrubezhny]

This PR makes it free of any use of odo preference view/add registry/remove registry and makes ~/.odo/preference.yaml file to be correctly initialized and ready to be used by odo (while we continue using it).

This removes the risk of hanging up for about 40 seconds while getting the list of configured Devfile registries in cases when a cluster is not accessible.

[datho7561]

Works well for me. Thanks, Victor!