-
Notifications
You must be signed in to change notification settings - Fork 7
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
Enhance primitive object display in the frontend #393
Comments
Do you need the backend to identify list-like object in the API? |
We should not try to give a representation to objects that don't have one. It is a choice of the user to represent things, and MediaItem is made to work around this need. In the future, we might want to offer the ability to create a visualization from data saved in the project. |
In the future, we should be able to create plots and charts from data stored in skore. @MarieS-WiMLDS suggests to limits the amount of series items. I would suggest to use Sylvain's suggestion for a start. |
For more information:
|
So what is proposed here is to call |
It is just an inspiration to design our own display options. How it should be implemented is another matter. |
Let's focus on #394 before this one. |
Solution suggestion @anasstarfaoui @rouk1 Primitive list:
Series:
Primitive dictionary:
|
This problem lacks proper framing, though the pain point remains valid. |
For now we use basic JSON serialization and code highlight.
Log lists / dict should be trimmed to avoid painful scrolling.
I think its hard to find a generic plot which can represent all sort of series, while remaining easy to understand.
Maybe we can just display a sample of the series when its too long ? As done by pandas in python
(0, 1, 2, [...], 3, 4)
.@rouk1 is there the same problem on list-primitive type?
@MarieS-WiMLDS @sylvaincom what do you think?
Keep in mind that, as for python list, the user can put whatever he wants in his series (str, number, str & number etc).
Originally posted by @thomass-dev in #378 (comment)
The text was updated successfully, but these errors were encountered: