The name map is now in libgnucash/engine/gnc-optiondb.cpp and named class OptionAlias. It is not public and so not available for custom reports to add their options to it.
As usual for GnuCash backwards compatibility is only with the last major release, though in the case of saved reports nothing significant has changed since GnuCash 3.0. If you encounter a saved report configuration contained in saved-reports-2.8 not being read please file a bug. If it's from saved-reports-2.4 or earlier you'll have to recreate them. Regards, John Ralls > On Apr 10, 2023, at 8:42 PM, Vincent Dawans <dawa...@gmail.com> wrote: > > In version 4, /libgnucash/app-utils/options.scm was the file in which a > list of old names and new names of report options that had been renamed > could be paired to maintain backward compatibility with saved report > configurations. This was via the option database code, inside > the new-names-alist function. > > How does that work in version 5 with the report option code rewrite? I find > ./gnucash/bindings/guile/options.scm but I don't see where I am supposed to > put the option renaming code in this version if it's even in that file. > > I assume the correspondence list from version 4 should still be somewhere > but a search on some of the old option renaming does not return anything. > Do we not keep backward compatibility for saved report configurations when > going to the next major version? Regardless, if I want to propose renaming > an option in a PR, what code do I need to put where to keep backward > compatibility? > > Sincerely, > > Vincent Dawans > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
