Project

General

Profile

Actions

action #89638

closed

libyui-rest-api does not report errors when querying wrong widgets, and debug labels cannot be query'd.

Added by JRivrain about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2021-04-12
Due date:
% Done:

100%

Estimated time:

Description

If we run a query like http://server:port/v1/widgets?debug_label=SomeText, it returns a json like the one attached (widgets.json, see also the corresponding dialog.json, those come from the "welcome" firstboot client) . So at first sight it looks like the query worked. But In fact, it is the same as querying "http://server:port/v1/widgets" without any arguments. We can observe the same with other elements, that are not "query-able" or non-existant (eg "widgets?class=YQWizardButton" or "widgets?notexist=nope").
It would make more sense to have a "widget-not-found" error in such cases.

Also, being able to query those debug_labels to identify pages could be very useful, as there is no (?) other unique way to identify pages/modules/clients otherwise, and those seem to be present on each of them.

https://github.com/libyui/libyui-rest-api was included into https://github.com/libyui/libyui and is a sub-directory.


Files

dialog.json (2.87 KB) dialog.json JRivrain, 2021-03-08 17:25
widgets.json (1.67 KB) widgets.json JRivrain, 2021-03-08 17:25
Actions #1

Updated by JRivrain about 3 years ago

  • Description updated (diff)
Actions #2

Updated by riafarov about 3 years ago

  • Target version set to SLE 15 SP3
Actions #3

Updated by riafarov about 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #4

Updated by oorlov almost 3 years ago

  • Target version changed from SLE 15 SP3 to Current
Actions #5

Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to New
Actions #6

Updated by JERiveraMoya over 2 years ago

  • Status changed from New to Workable
Actions #7

Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #8

Updated by JERiveraMoya over 2 years ago

Completed installation in a VM. The way to build the project has changed quite a lot since last time I checked and using a VM with TW I had to install the following in order to build all projects:

sudo zypper in git-core
sudo zypper in make
sudo zypper in cmake
sudo zypper in gcc (?)
sudo zypper in gcc-c++
sudo zypper in "rubygem(libyui-rake)"
sudo zypper in rpm-build

rake build_dependencies:install
sudo ./build-all
Actions #9

Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Feedback
Actions #10

Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF