question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Minor improvements for the HTML report

See original GitHub issue

The HTML report is a bit more verbose than it needs to be

Variable user_id is not declared with a var statement. Use var or the local scope, or otherwise clarify the scope

In file C:\Users\zac\Documents\GitHub\CFLint\build\libs.\linenumber.cfm, line 2

At line: 2, at column: 2

In function test()

Expression: user_id

  • line number is repeated twice, may add the column number to the file reference and remove the At line: 2, at column: 2 line and extra new line?
  • the variable user_id could be made bold for clarity
  • expression (i.e. code snippets) could be wrapped in <pre></pre>
  • ‘In file’ is kind redundant before to the file path
  • does the warning need to be repeated in the details section, it’s already the warning column?

Variable user_id is not declared with a var statement. Use var or the local scope, or otherwise clarify the scope

C:\Users\zac\Documents\GitHub\CFLint\build\libs.\linenumber.cfm, line 2, column 2

In function test()

Expression: user_id

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:7

github_iconTop GitHub Comments

1reaction
TheRealAgentKcommented, Jul 31, 2017

Fixed that @zspitzer

1reaction
TheRealAgentKcommented, Jul 30, 2017

Ha, nothing is easy sometimes.

So, the HTML report gets created by XSLT from Findbugs XML which itself comes out of CFLint XML by XSLT. sigh 😃

In a nutshell - some of the blurbs I get to get into the HTML report can’t be easily changed.

I made two small fixes:

  • does the warning need to be repeated in the details section, it’s already the warning column?
  • ‘In file’ is kind redundant before to the file path

The other items I’ll get back to in the output/report rewrite for 2.0.

Read more comments on GitHub >

github_iconTop Results From Across the Web

HTML Reports and Architecture Improvements - LogicMonitor
HTML Reports and Architecture Improvements ... You may notice minor changes in header information and layout as a result. With the HTML view ......
Read more >
WebLog Expert Version History
Fixed HTML and PDF report generation on systems with high DPI settings. Improved recognition of Bing searches. Minor improvements ...
Read more >
Six Tips for Making a Quality Report Appealing and Easy To ...
To attract and hold users' attention, your quality report needs to be designed in a way that: Looks appealing and approachable at first...
Read more >
What's New in CSS HTML Validator
Version 2022/v22 contains many updates and improvements you'll want to have: Improved and updated support for HTML5; Improved and updated support for CSS ......
Read more >
Version History - Reportizer
Improvements in exporting reports to HTML. Improvements in GUI. Minor changes and bugfixes. 6.1.8.14 (10/21/2018). Improvements in interface when working ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found