[MDSAL-72] Javadoc contains unwanted html entity replacements Created: 04/Mar/15  Updated: 09/Mar/18  Resolved: 22/Feb/16

Status: Resolved
Project: mdsal
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Michal Rehak Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Duplicate
duplicates MDSAL-46 Generated javadoc contains symbols of... Resolved

 Description   

Current javadoc contains html formatting tags (p, pre, i) but surrounding < and > characters are escaped via html entities which results into unformatted javadoc.

example:

  • <p>This class represents the following YANG schema fragment defined in module <b>node-error</b>
  • <br>(Source path: <i>META-INF/yang/node-errors.yang</i>):
  • <pre>
  • notification bad-request-error-notification {
  • description
  • "Model for ofp_error-Type=1, Request was not understood.";
  • leaf type { * type error-type; * }
  • leaf code {
    ...

Please do not escape formatting tags.



 Comments   
Comment by Robert Varga [ 18/Mar/15 ]

In order to address this cleanly we'd have to check for HTML well-formedness – which makes this a new feature for Beryllium.

Generated at Wed Feb 07 20:08:34 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.