Reported by jteh on 2013-11-08 08:15
config.validateConfig was removed as part of #667, since NVDA no longer uses it. However, it seems some add-ons such as Windows 7 Magnifier depend on it. Since this function wasn't marked as private (even though it probably should have been), we need to keep it for 2013.3 but deprecate it in the next release, as this is what we generally promise for public API stuff.
After that, the question is whether we should keep it in some sort of utility module. My feeling is that we shouldn't, as I think it'd be ideal to have add-ons use NVDA's configuration so they can benefit from profiles and so we can avoid constant reinvention of the wheel. Add-ons that really need this can include it themselves.
Reported by jteh on 2013-11-08 08:15
config.validateConfig was removed as part of #667, since NVDA no longer uses it. However, it seems some add-ons such as Windows 7 Magnifier depend on it. Since this function wasn't marked as private (even though it probably should have been), we need to keep it for 2013.3 but deprecate it in the next release, as this is what we generally promise for public API stuff.
After that, the question is whether we should keep it in some sort of utility module. My feeling is that we shouldn't, as I think it'd be ideal to have add-ons use NVDA's configuration so they can benefit from profiles and so we can avoid constant reinvention of the wheel. Add-ons that really need this can include it themselves.