René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Refactor Query/Flied classes `.get_info` and related methods for better programmatic use","articleBody":"### Description\r\n\r\nThe `Query` class (and the related `Field` class) from the `query_builder` module has some functionality to display information about a query at hand and which fields,enums etc. one might add to it. A lot of this functionality is related to the `.get_info` method.\r\nCurrently this method prints the information to stdout when it is called. This has two main disadvantages.\r\n 1. The method name is misleading as it doesn't \"get\" anything but instead \"prints\" something\r\n 2. It's difficult to build applications on top of the query_builder class that make use of the `.get_info` information in their own way (i.e. don't do naive printing). Such an application could be a dashboard for data exploration.\r\n\r\nI would suggest to refactor `.get_info` and related methods to return a data type, for instance a dict or a named tumple containing the information, such that it can be build upon. Addionally one could extend the Query/Field class to additionally retain its info printing funcitonality based on the new `.get_info` but under a different name. For instance `.print_info`.","author":{"url":"https://github.com/KonradUdoHannes","@type":"Person","name":"KonradUdoHannes"},"datePublished":"2020-05-11T05:18:20.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/76/datenguide-python/issues/76"}