#2409: last call for options keys consolidation ----------------------------------+----------------------------------------- Reporter: martinl | Owner: grass-dev@… Type: task | Status: new Priority: blocker | Milestone: 7.0.0 Component: Default | Version: unspecified Keywords: standardized options | Platform: Unspecified Cpu: Unspecified | ----------------------------------+-----------------------------------------
Comment(by wenzeslaus): Replying to [comment:25 martinl]: > Replying to [comment:24 martinl]: > > Do we prefer to leave as it is or change to > > > > {{{ > > background_color > > }}} > > > > ? > > > > Then it can be abbreviated to > > > > {{{ > > bcolor > > }}} > > > > but not to > > > > {{{ > > bgcolor > > }}} > > The attachment:renamed_options.diff adds to the parser support for renamed options. Eg. > > {{{ > d.erase bgcolor=black > }}} > > will continue to work with appropriate warning > > {{{ > WARNING: Please update the interface of the module: option <bgcolor> has been renamed to <background_color> in GRASS 7.0 > }}} > > Make sense to you? We need something like this for a long time already. It is really good as long as it is used as you are proposing that is to maintain backwards compatibility. I wouldn't like to see that used as a way to provide different names for one option. -- Ticket URL: <http://trac.osgeo.org/grass/ticket/2409#comment:35> GRASS GIS <http://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev