You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging 'System.ArgumentException: Property Get method was not found.' at XmlDoc2CmdletDoc.Core.Domain.Parameter.get_DefaultValue() I eventually found it means you are messing a get'er on a Property like
public SomeObject SomeObject
{
set { _id = value.SomeRef; }
}
It would be nice to know on which cmdlet, property or attribute it fails to easily correct the situation. At least the above will give guidance to others.
The text was updated successfully, but these errors were encountered:
If a parameter doesn't have a getter, we cannot read it to determine its default value. In that situation, we can simply not include a default value in the help docs.
Should we record a warning for this scenario? Bear in mind that if the -strict flag is enabled, warnings are treated as errors and the tool will fail? I'm leaning towards including a warning. Whenever we encounter a Parameter with no getter, I think it's far more likely to be evidence of a coding error than a deliberate choice, and by emitting a warning, it will highlight this deficiency.
While debugging 'System.ArgumentException: Property Get method was not found.' at XmlDoc2CmdletDoc.Core.Domain.Parameter.get_DefaultValue() I eventually found it means you are messing a get'er on a Property like
public SomeObject SomeObject
{
set { _id = value.SomeRef; }
}
It would be nice to know on which cmdlet, property or attribute it fails to easily correct the situation. At least the above will give guidance to others.
The text was updated successfully, but these errors were encountered: