"Field" disappears when new_type is used about ldoc HOT 5 CLOSED

I encountered this issue as well. After fiddling around for several hours, I wasn't able to find a solution that didn't have weird duplication issues or require modifying ldoc.lua. I chose the latter.

--- ldoc.lua.old        2013-01-21 12:38:42.942227984 -0700
+++ ldoc.lua    2013-01-21 12:39:05.210338397 -0700
@@ -140,12 +140,12 @@
 end

 -- new tags can be added, which can be on a project level.
-function ldoc.new_type (tag,header,project_level)
+function ldoc.new_type (tag,header,project_level,subname)
    doc.add_tag(tag,doc.TAG_TYPE,project_level)
    if project_level then
-      ProjectMap:add_kind(tag,header)
+      ProjectMap:add_kind(tag,header,subname)
    else
-      ModuleMap:add_kind(tag,header)
+      ModuleMap:add_kind(tag,header,subname)
    end
 end

I use it like: ldoc.new_type("struct","Structs",false,"Fields")

from ldoc.

On Mon, Jan 21, 2013 at 9:45 PM, SolraBizna [email protected] wrote:

I encountered this issue as well. After fiddling around for several hours, I wasn't able to find a solution that didn't have weird duplication issues or require modifying ldoc.lua. I chose the latter.

That's a good solution, thank you. It's necessary to specify what the
subfields (if any) of a new type are.

I will update the source and the docs accordingly.

from ldoc.

On Thu, Jan 24, 2013 at 2:10 PM, steve donovan
[email protected] wrote:

I will update the source and the docs accordingly.

Right, uploaded.

Should be able to grab 1.3.2 from the tags page:

https://github.com/stevedonovan/LDoc/tags

from ldoc.

Can we close this issue?

from ldoc.

Thanks for fixing this.

from ldoc.