Age | Commit message (Collapse) | Author |
|
|
|
|
|
declared by itself
|
|
|
|
|
|
|
|
Closes #334
|
|
An updated local version of mdoc started causing test output changes which clashed with the CI build agent's config. So this change removes this functionality from the integration tests, and adds a few unit tests that tests the exception functionality. Closes #341
|
|
Removed namespace when return type is generic
Added integration tests
Added unit test
Add RefType attribute to ReturnType element
Closes #230
|
|
Resolves #220
|
|
Based on the pull request #170
Node <Implements> with subnodes <InterfaceMember> show which member(s) of interface(s) is(are) implemented
<Implements> and <InterfaceMember> are added to monodoc-ecma.xsd
Added the integration test `check-monodocer-members-implementation`
Closes #158
|
|
Corrected VB and C# formatters
Edited integration tests
Closes #137
|
|
Removed line from method `GetFieldConstValue` that forbade obtaining the value for `enum`
Edited integration tests
Closes #28
|
|
Closes #118
|
|
Closes #78
|
|
Previously, mdoc simply used the compiler-generated method names for operators, such as `op_Multiply`, instead
of `operator *`. This releases fixes that for all unary, binary, comparison, and conversion operators.
Closes #82
|
|
Now using MSBuild.
Updated some test data to reflect newly thrown exceptions.
Updated to a newer version of NUnit.
|
|
Closes #6
|
|
This was inadvertently removed in https://github.com/mono/mono/commit/611a43ee0f672adbac3e25dc77731843a3d10cf1 from MulticastDelegate.CombineImpl().
Add the type check back in the Delegate base class, we already do the same in Remove().
Add unit tests to cover the behavior to the corlib test suite. (reverted from commit f29878dc713f4e148fe0a1e703fae8929e6fb6e0)
Needed to update some monodoc tests to match that an exception is now thrown again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Commit 0a2c38df changed Delegate.Remove() so that it uses
Locale.GetText(), which thus introduces additional exceptions which
can be possibly thrown from Delegate.Remove().
This is similar to the situation in corlib/3d3fe6af (added
Locale.GetText() use) and mdoc/574dbc8e (updated unit tests).
|
|
|
|
3d3fe6af (among other commits...) "broke" the `mdoc` unit tests, as it
did two things:
1. It added a new codepath calling string.Format(), thus introducing
a new set of exceptions.
2. Due to an `mdoc` bug, (1) resulted in a stack overflow on OS X.
(1) demonstrates that the mdoc unit tests might be too brittle.
(2) was fixed in 04bf9ad.
The problem with 04bf9ad, though, is that it resulted in a gigantic
~212MB diff, because while the recursion was "fixed", we could still
process the same method multiple times, resulting in _lots_ of
duplication, e.g. System.String.get_Chars() would be repeated hundreds
of times for a given exception.
Improve the source reporting mechanism so that instead of a
List<MemberReference> we use a HashSet<MemberReference>, listing each
source location _once_ instead of repeating them.
The _formatting_ of the <exception/> element is also changed so that
each source location is on its own line, making it easier to read and
review the locations.
|
|
Nested `protected` types are accessible from subclasses, and thus
should be documented just as `public` nested types are.
|
|
|
|
|
|
`mdoc update --delete` is supposed to remove XML for types and type
members that are no longer present. This works sanely if the
type/member has only one assembly version in it, but once a member is
found in multiple versions, --delete only removes for the assembly
version currently being processed, and thus the member may stay in.
Ordinarily this is sufficient, and is why the HTML output lists the
assembly versions the type/member is found in.
However, then we introduce -fno-assembly-versions, which removes the
version store (if present) and doesn't re-generate. Thus, when both
are present, we would expect types and members to be removed,
irregardless of any pre-existing version information (because that
version information will be removed). This didn't happen. Worse,
because we kept re-processing version information, we'd ~never remove
any members even after repeated invocations, because we weren't
properly skipping the version store. Oops.
Fix the interaction, and Add tests so we ensure this works.
|