Splunk Apps » Lookup Editor

• makeRowJSON
• timeRenderer

Questions:

• What happens when a string value is supplied?
• What happens when an epoch is provided?
• [Answered] How does includes_microseconds get set?
  • lookupRenderer(): when it sees _time
  • getDefaultEditor(): when it sees _time
• Does formatTime get called with microseconds upon load?
• What happens when formatTime is told to use microseconds?
  • It edits correctly but gets the wrong value when the lookup is reloaded
  • It appears to load a ms value
  • It also converts the value to ms when it posts to the endpoint
• [Answered] Where does formatTime get called?
  • getTimeRenderer()
  • getDefaultEditor(): may only apply to CSVs though
• [Answered] What the use cases?
  • https://lukemurphey.net/projects/splunk-lookup-editor/wiki/Test_Plan#section-4
• Is formatTime() correct to multiply the time by 1000 when it include ms?

• [Fixed] Editing is saving the value with microseconds
• The initial load is assuming that the values include microseconds
• moment assumes that a provided integer has microseconds
• Entering an epoch causes two posts
• Double post is not due to timeRenderer() nor makeRowJSON() changing the time value nor the editor (assigned in "editor:")
• lookupRenderer() is not used for KV lookups
• Getting a source of timeValidator for the second post
• formatTime() is getting the string value in string format that has already been converted
• formatTime() is doing the right thing upon editing
• The persisting to the KVstore collection isn't causing the problem
• Not setting the column type to "time" in TableEditorView::getColumnsMetadata()
• There is a correctTime format option: https://handsontable.com/docs/7.0.0/demo-time.html