Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

generated xml for enumerations handles values differently to other members #25

Open
barry-jones opened this issue Jan 12, 2019 · 0 comments
Labels
question Further information is requested

Comments

@barry-jones
Copy link
Owner

Normally a members fields, properties, methods etc are stored as an entry under an entries element with details of the id, type naem and cref etc e.g.

<entries>
    <entry id="4294969814" subId="" type="constructor" visibility="protected" cref="M:TheBoxSoftware.Reflection.Signatures.SignatureConvertor.#ctor">
        <name>SignatureConvertor()</name>
    </entry>
</entries>

Enumerations are handled as values.

<values>
    <value>
        <name>MethodDef</name>
        <description>
            <summary>
                <text>Signiture which describes the signiture or of a method or global function. </text>
            </summary>
        </description>
    </value>
</values>

Consider converting the same format as all of the others to simplify XSLT processing.

@barry-jones barry-jones added the question Further information is requested label Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant