- service responses
- disable runtime sort
- first auto-format feature
- properly set version inside sources
- fixed #115
- show name and version in HA console
- sort by column clickable header
- some init error checks
- fix table update on entity deletion
- move formatting before
modify
operation - fix ordering with special chars
- allow dotted object notation, fixes #86
- allow clicking single row entities #102#
- allow
_name
similar to_data
, fixes #95 - only refresh tables, if needed
- improve docs
- multi-column sorting, fixes #67
- some doc updates
- entity.attributes.state now available through special data: '_state', fixes #51
- docs: add example for multi include/exclude filtering; fixes #48
- docs: add new special 'data' fields
- remove redundant 'text-align: left' from default 'thead th' style; fixes #52
- allow 'icon' as data to show the entity's default icon - fixes: #68, addresses #63
- remove pre/suffix whitespaces in multi-data-column selection 'parser'; fixes #42
- introduce and revert more aggressive null-cell handling, need's a more robust approach
- BACKWARD COMPATIBILITY / DEPRECATION WARNING: 'data' is replacing all other
column
selectors i.e., 'attr_as_list', 'prop', 'multi', 'attr' shall not be used anymore. Initially only a console.log() warning will be shown, soon this will change to console.warn(), then console.error()
- added
multi
instead ofattr
orprop
for column/cell contentsmulti
consists of list of string-pairs e.g., ["attr", "node_id"]- allows multiple attributes or properties, whatever to be put into a single cell
- together with
modify:
andcss:
enables content-conditioned styling, like a cell changing cell-color depending on any state/attr/whatever - 'multi_delimiter' further allows to descide how the multiple items within one cell get concatenated, i.e., which delimiter is to be found between the chunks
- added
icon
configuration for adding an icon to column headers
- added
css
configuration parameter to allow arbitrary modifications of the used CSS styles.
- allow sorting for multiple
attr_as_list
columns by using anid
- added
align
param to set text-alignment within a column including the header - added
suffix
to add units or similar static after the actualy contents - added
prefix
which does what the name implies ;) - smaller bugfixes like keeping the entity order consistent if no sorting is applied
- fixed #28 and #23, which mainly occured due to #24, which changed the "empty" behavior output of 'get_raw_data()' away from not-iterable 'null' to an empty Array
- fixed #26: use correct CSS variables to be compliant with theming
- cleaned front-page README.md and introduced the 'docs' directory to keep all documentation there, included template for new doc generation
- added necessary files (info.md + hacs.yaml) for HACS
- fixed #22: using now proper 'strict' JavaScript
- fixed #25 with PR #27: introduced auto-entities support, thanks @SBado
- now with 'clickable' rows to show the entity_id's popup dialog for further information
- more or less full re-write introducing DataTable and DataRow as data representation objects
- minor improvements, code tidyness, changes for clickable rows started
- exluding mulitple items fixed
- sort_by works now also with 'props' columns thx @andreassolberg
- regular expressions now concated and applied instead on after another
- lots of cleanups
- flex-table-card now part of 'custom-cards' organization
- added 'modify' to change cell/col contents using javascript's: eval()
- for 'prop' column contents 'object_id' and 'name' are made available to match: https://www.home-assistant.io/docs/configuration/state_object/
- Functionality existing as initially planned:
- arbitrary number of columns
- regex based matching of anything that can be accessed through the hass-object (states, attributes, any properties of entities, anything that's visible)
- restrictions in rows possible
max_rows
- sorting by chosen column available
sort_by
(ascending and descending) - column(s) might be hidden (to realize a hidden sorting)
hidden
strict
forces each row to be completly filled with matched content, if not the row will be dropped- using
attr_as_list
allows easy data visualization from external sources, likeappdaemon
- in "productive" use now, will shortly go in Version 1.0
- initial commit, forked from entity-attribute-card
- The goal is to provide a flexible table visualization for Lovelace.