Community
Participate
Working Groups
When an Interface declares a config param to be 'readonly', that property should be inherited by Modules that implement that interface. Then, a Module implementer need not explicitly restate this 'readonly' attribute if they override the default setting. As a result, if the Interface restrictions are lifted (e.g., the Interface removes the 'readonly' attribute making the field writeable), Module producers would not be required to rebuild against the new interface. Some initial quick testing (with the Interface and Module in the same package) seem to indicate this is supported. So this enhancement is perhaps simply a request for a test to validate the use case is supported.
The current implementation allows the module writer to override the config parameter without the readonly attribute _but_ the readonly property is "lost". However, this is arguably correct: the inheriting module is declaring that it will allow both gets and sets whereas the underlying interface simply requires gets. The attached tar contains a set of package that allows experimentation with this behavior.
Created attachment 157026 [details] packages that illustrate readonly behavior
nothing to be done (I think)
