Development

SfliveParisDevMeeting (diff)

You must first sign up to be able to contribute.

Changes between Version 6 and Version 7 of SfliveParisDevMeeting

Show
Ignore:
Author:
lsmith (IP: 77.58.253.248)
Timestamp:
03/08/11 10:11:19 (7 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SfliveParisDevMeeting

    v6 v7  
    20204) overwriting bundle parameters 
    2121 
    22 we agreed that we would specify in the documentation that anything specified in config files while technically overwriteable they are not to be considered extension points. therefore anything that should be configurable in a Bundle should be explicitly exposed in the Bundle's configuration. we also discussed if we should remove unnecessary use of parameters (like parameters for class names which are not meant to be configurable). there was a bit of back and forth here. one side was to discourage users from shooting themselves in the foot (aka those who do not care about the warning that we do not maintain BC in things not exposed in the config), while others said they might still want to do and just deal with BC breaks as they occur (which should not be too often). IIRC we in the end decided that with a clear doc warning it should be clear enough, so no change
     22we agreed that we would specify in the documentation that anything specified in config files while technically overwriteable they are not to be considered extension points. therefore anything that should be configurable in a Bundle should be explicitly exposed in the Bundle's configuration. we also discussed if we should remove unnecessary use of parameters (like parameters for class names which are not meant to be configurable). there was a bit of back and forth here. one side was to discourage users from shooting themselves in the foot (aka those who do not care about the warning that we do not maintain BC in things not exposed in the config), while others said they might still want to do and just deal with BC breaks as they occur (which should not be too often). in the end there was no clear agreement if its enough to just warn users in the docs or if we have to prevent users from "shooting themselves in the foot" by going through all the xml configs to remove unnecessary parameters, thereby preventing users who accept the BC break risk from easily overriding internals
    2323 
    24245) protected vs private