It may seem simple as you may have some data in tables (hello, MySQL) and you want them on a web page (hi, <table>). But you start joining data from other tables and you end up displaying a tree in a table. How? You never know how to do it until you try to use that. UX!
(2/6)
(2/6)
But if you have tree-data, tree-database (hello, Mongo), and tree components on website, you still need tables to present the data of similar structure. It's all 2D and are brains are trained to get information presented as combination of 2 axes. Hello, tables!
(3/6)
(3/6)
But tree components in UI are the problem by themselves. How to make data reactive, how to edit and move branches, how to display long lists, how to search & filter in trees! Not so many pre-built components solve these issues. And they may work pretty bad for YOUR data.
(4/6)
(4/6)
What if you make CSV export for clients. You know, no one would edit your JSON files manually. But everyone can edit data in Excel!
Putting tree data into CSV doesn't make nice! Trees in CSV are just awful! Data duplication, internal values, etc. Nah!
Putting tree data into CSV doesn't make nice! Trees in CSV are just awful! Data duplication, internal values, etc. Nah!
For most of my time as #webdeveloper, I convert trees to tables, group data, and display it. Each time I do something differently. So I never get bored!
🤠
(6/6)
🤠
(6/6)
It looks like when tweeting on a general #webdev topic I need to tag as many web frameworks as possible because this thread applies to all of them!
#laravel #symfony #rails #django #react #vue #emberjs #svelte #Angular #nuxtjs #Nextjs
#laravel #symfony #rails #django #react #vue #emberjs #svelte #Angular #nuxtjs #Nextjs
• • •
Missing some Tweet in this thread? You can try to
force a refresh
