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

Feature 270 show error in streamedtable #275

Merged

Conversation

ThePhisch
Copy link
Contributor

Data is streamed to the frontend in the form of ViewModels, these viewmodels can also wrap information on errors that may have occurred. This PR introduces the ability to view these errors from within the UI implemented for the StreamedTable. It also replaces all the core entities with ViewModels, so that the errors can be passed and displayed properly. Replaces the old entity-based fixtures with viewmodel-based ones.

Anton Schwarz added 2 commits August 4, 2023 16:12
Added `TableErrorstatus`, added `TableErrorreader` and appropriate
fixture

* `TableErrorreader` works together with `TableErrorstatus` in the
  `TableFooter`: an indication of errors is shown in the status "pill"
  (which sits among the pagination and fetchstatus), but the detailed
  view can be opened and is shown in `TableErrorreader`.
* Added a fixture `mockBaseVM` to mock the base view models (and
  especially whether they have errors or not: you can pass "none" |
  "some" | "all" and it will have some or all errors then.

Connected Tableerrorstatus and Tableerrorreader via the footer

Can close TableErrorreader from within the component
wrote viewmodels to wrap the core entities in `BaseViewmodel`, added
fixtures.
@ThePhisch ThePhisch merged commit 08fc9e6 into rucio:master Aug 4, 2023
7 checks passed
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

Successfully merging this pull request may close these issues.

1 participant