Add label functionality for details table #111
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samussiah
reviewed
Mar 26, 2018
| var detailVars = vars.details; | ||
| var details = details.map(d => { | ||
| var current = {}; | ||
| detailVars.forEach(currentVar => (current[currentVar] = d[currentVar])); | ||
| detailVars.forEach(currentVar => { | ||
| if (currentVar.value_col) { |
samussiah
approved these changes
Mar 26, 2018
|
@samussiah This works as expected across three browsers. The listings appears with nothing added to the Details fields. Then when AESER is added with Label Sev it appears as one column with the label Sev. Same results for AESEV and Sev. When both are added it creates 2 columns. When the Labels are removed the column label defaults to what is in the Value Column field. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #105