`--append` to reports
See original GitHub issueAs discussed here is very helpful for the viewer to keep backwards compatibility to keep the previous comment collapsed.
<details id="SHA">
<summary>SHA</summary>
CML REPORT
</details>
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
append - MATLAB Report Generator - MathWorks
append ( report , content ) adds the specified content to the specified report. If the report is not already open, the append...
Read more >PSA LRW - Reports: How to append reports - ParishSOFT
Go to Ledger Report Writer, and click on Append Statements. Use the Select Statements dropdown to choose the custom ledger statements you want ......
Read more >Append a Report - EQuIS 7.22.2 - EarthSoft
The option to Append report output in EQuIS Professional enables reporting different unit types together without conversion errors.
Read more >Append Report Text VI - NI - National Instruments
Appends text to the selected report. Wire data to the text input to determine the polymorphic instance to use or manually select the...
Read more >Appending a Report - Incident Tracker
After a report is submitted, new information can be appended to the report. This is different than editing a report because no original...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@duijf it seems that you are effectively talking about asking users to not use the
--update
flag. Not using the flag would preserve all reports (default behaviour).Not sure if we should be making CML itself preserve reports in-place with collapsible headings if
--update
is used. I’d suggest a new (feature request) flag--append
for that…I’d say if the platform doesn’t support edit history, then users requiring history should simply not use
--update
(just use--pr
). I’d downgrade this top2
or even just close?