Table Panel: Format specific fields as pretty (human readable) JSON #321
Conversation
|
Sounds interesting. Maybe I can use this feature to display webservice request/resonse values. |
|
You shouldn't be using ng-html-bind-unsafe here, any xml embedded in the json string will render improperly. You should be using ng-bind-html with a function to properly escape xml sequences. |
|
I'm using |
|
I think it will be great if the formatted json text will not only be displayed in the details. The text in the table row should formatted, too. |
|
Hm, how do you imagine to format the text in the table row? If the text is prettified it will use a lot of space and hence don't fit to the space available in a single table row. |
|
yes you're right. I used this feature to format webservice requests. I my case the unformatted text is very long, too. I think you're right it makes no seems to format the text in the table. Maybe a table column needs a properties ,show only the first line'. |
|
I moved the changes to the branch |
…reported every 10s Full stack traces are logged in debug Closes elastic#321
Spliting out the event manager config since Carpenter and Link use it di...
* Replaced mathjs with tinymath in math.js. Wrote unit tests for math.js. Upgraded tinymath * Added string and bool columns to testTable for math.js tests. Added unit tests for math.js * Added columns to testTable in math.js test file * Upgraded tinymath to version 0.1.8 * Created function to convert datable to math context for math.js * Replaced pivotObjectArray with datableToMathContext * Wrote unit tests for math.js * Fixed unit test for math.js. Removed references to mathjs package in math.js * Uncommented line to run server tests * Refactored math.js test file * Replaced every instance of Object.value with value from lodash * Create test file for pointseries. Wrote unit tests for pointseries. * Added unit tests for pointseries * Moved 'server/functions/pointseries.js' to 'server/functions/pointseries/index.js'. Updated unit tests. Created lib folder for pointseries helper functions * Removed map function from lodash * Added unit test for pointseries.js * Refactored pointseries and replaced mathJS functions with tinymath functions * Removed common/lib/math.js. Replaced reference to math.js with tinymath in handlebars.js. * Replaced mathjs with tinymath in datacolumn.js * Refactored pointseries.js. Replaced mathjs with tinymath. Removed unused lodash functions * Removed mathjs package and generated docs * Fixed unit tests. Fixed getType function in math.js * Moved getFormObject function to a separate file. Imported getFormObject into datacolumn.js. Rewrote getFormObject to work with parse from tinymath * Rewrote getFormObject to work with parse from tinymath. Wrote unit tests for getFormObject * Added unit test to test runtime of pointseries using demodata * Updated demodata test * Removed console logs * Updated runtime test for pointseries * Removed runtime test for pointseries * Added error handling for empty datatables in math.js. Updated unit tests * Upgraded tinymath to 0.1.9 * Changed error message thrown in getFormObject, updated unit tests * Created test datatables file * Cleaned up tests for math.js. * Wrote tests for datatableToMathContext * Cleaned up unit tests for pointseries * wrote tests for isColumnReference * Renamed getType in pointseries to getExpressionType * Pulled out functions out of pointseries into lib functions and added imports to pointseries * Wrote unit tests for getFieldType * Wrote unit tests for getFieldNames * Wrote unit tests for getExpressionType. Refactored pointseries. Updated unit tests for pointseries helper functions. * Removed mode from dropdown menu in SimpleMathFunction * Cleaned up unit tests for pointseries and helper functions
Hi,
i've implemented a feature, to show json data in table fields as pretty formated JSON. We use this in our error logging, to get an better insight into our php generated debug backtraces.
Is anyone interested in sharing this feature?