Open jum-s opened 10 months ago
imo, the best illustration is the live data itself: all those settings are available from the UI they parameter, it's even a bit redundant to have them in the settings too; I would rather get rid of the repetition in the settings than get into mocking data :sweat_smile:
indeed mocking would be defined here as an "artificial" way to fetch some fitting data for the component. I imagined retrieving some real user data for the matter.
Some settings strings can be quite difficult to understand without graphical help. Example with
Display
section: Now that most of the app is based on Svelte components, we might be able to explore importing components in settings, mock some data and display what this text actually means. Mocking data might also be a tricky/healthy isolation exercise.