Table, Bro

Call this first, once per session. It explains how Table, Bro works, a Web Components table engine on top of the UI library of your project, and which tool to use when; shows a minimal table for your target and skin; lists the topics of get_docs. Do not call it again in the same session: use get_docs. Example: {"target": "angular", "skin": "mat"}

Returns one topic of the reference or one page of Docs with its code by its name, the two topics that match a query best, or all topics with their summaries. Use it for questions about the API and for changes of an existing table; get_started already gives the topics basics and workflow. Example: {"topic": "server-mode"} or {"query": "row height"}

Profiles the project: the packages of Table, Bro and their version, the framework, the registered skins, the CSS, the custom elements, the tables, and the problems of the setup with their fixes. Call it once before you add code to a project, and when a table does not render. Pass skins.registered as the skin and framework.name as the target of the other tools. Not for questions about the API. Each list keeps its first 20 items; omitted counts the rest. It reads the project as text and writes nothing. Example: {}

Checks a table spec, a BroTableSpec (get_docs, topic spec), and reports every error and warning with its path, what is wrong and the fix. Use it while you draft a spec. generate_code runs the same check first and returns the same report for a spec with errors. Example: {"spec": {"specVersion": 1, "rowType": "Product", "fields": [{"name": "title", "type": "string"}], "cols": [{"title": "Product", "name": "title"}]}, "skin": "mat"}

Generates the code of a new table from a spec or from a built-in spec: the files, the setup of the project, once per project, and what is left to finish by hand. The fillings are the templates of the cells, the rules of the custom filters and the bodies of the functions of the skin config (get_docs, topic fillings); without them the files keep TODOs. A spec with errors returns the report of validate_spec and no files. For one cell, the row details or the filters of an existing table use scaffold_component. Example: {"builtinSpec": "products", "target": "angular", "skin": "mat"}

Scaffolds one component for an existing table: a custom cell, the element of the row details, or the filters of the Filter Drawer, and tells how to connect it to the page: the registration of the element and its column, or the container of the drawer. For a new table use generate_code, which writes its cells too. Example: {"kind": "cell", "target": "angular", "skin": "mat", "rowType": "Order", "fields": [{"name": "status", "type": "string"}], "name": "status", "shows": "the status as a chip", "reads": ["status"]}