Thanks @loicknuchel for your suggestion.
I've tried using it, and it looks great. But when I've tried using it used it a
couple of times, I haven't found it very useful, and I give up after a minute
or two. I think the main issue is that it doesn't load all the tables at the
start, so you can end up with just a couple of tables showing (e.g. you click
on "acls" from the suggestions list, and then click "users", and then that's
kind of it? I can't see how to click to add more). There's a search box, but
people who are exploring the db don't know what tables to search for.
I think it would be more useful if all the tables were shown, and nicely laid
out, but perhaps that's overwhelming or unclear without manual arrangement and
grouping. As far as I understand, that's a paid feature.
I realise that I'm not the target user for this, since I obviously know the
overview of the database structure and how everything works. But for the
details I wouldn't use it either, because annotate_models puts the information
we need into the model files, i.e. closer to where we work.
So my request here is to other contributors, particularly new contributors -
can you try it out please? Have you found this useful, and if so, what did you
learn? Do you need a whole-database overview when you start working on the
project?
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5308#issuecomment-2473316475
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5308/c2473316...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
