Conversation
Contributor
|
From my perspective, this is a practical solution for now. The users get the information they need, and we and @oliversamoila and @thibsy have the time to create a nearly perfect solution within the KS. We could discuss if the listing of the used question types is needed. But this is a minor detail. |
Contributor
|
As this is a local change in T&A, we can merge this right after the approval from @thojou - the discussion if the we need a list of used question-/answer-types from a technical perspective could be taken place at the next techquad meeting on 01.10.26 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi all
This is not the most beautiful solution in the world, but I think conceptually this is the soundest way, I could come up with to get the situation here unstuck. Instead of even trying to include the summary information in the table, why not just add it above? The slight inelegance comes from the lack of facilities in the UIComponents to actually address this, a lack that is completely understandable, but cannot be remedied as part of a bugfix.
See: https://mantis.ilias.de/view.php?id=45093
The solution would look like this in the test:

and like this in the pool:

You also see in the screen shots, that the summary in the pool does on purpose not take into account any filtering.
I added the information about the contained question types, but this can clearly be removed again. I just thought, as we are creating this summary section, why not add some more useful information. The drawback: It pushes the other information on the screen further down. I've no strict opinion on this and defer it to you.
What do you think @thojou and @dsstrassner ?
Best,
@kergomard