#492 closed defect (bug) (fixed)
Wiki formatting should be disabled in code reference
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Developer Hub | Keywords: | |
Cc: |
Description
See the screenshot.
Attachments (2)
Change History (14)
#2
@
11 years ago
Side note: There was some discussion in the parser repo about supporting markdown in phpDoc content. I'd almost like to see us employ something like Markdown on Save or similar when the data is parsed, either that or actually handle markdown on display in the code reference. I wonder if that would cut down on "wiki formatting".
This ticket was mentioned in IRC in #wordpress-meta by sams. View the logs.
11 years ago
#4
@
10 years ago
- Resolution set to invalid
- Status changed from new to closed
This is an issue with characters in the inline docs not being properly escaped. DrewAPicture is investigating the method for escaping characters. This ticket will need to be re-opened on core trac.
#5
@
10 years ago
Worth noting that a large amount of these issues will be alleviated by the ongoing changes happening here: https://core.trac.wordpress.org/ticket/28298
#6
@
10 years ago
- Resolution invalid deleted
- Status changed from closed to reopened
Found another instance on https://developer.wordpress.org/reference/hooks/action/, see the screenshot.
How do we properly escape the characters in this case? The page content doesn't look like it's taken from the current admin-post.php file at all.
FYI: The example in the screenshot comes from the get_terms reference.