Very soft deprecation – just want the new name to show up on the README/docs. Probably won't even give a warning message for this change for a while (if ever).
Also adds a test of Preferences.jl by injecting custom versions of the key functions. Still not as good as an actual test of the set_preferences! interface, but still gives it a chance to walk through all the logic.
coverage: 99.057% (-0.6%) from 99.682%
when pulling a766a56ae5ed167be91d4ecf8c5cbde8fe00b0cc on consistent-preference-name
into 110fe2f84c12c4cce02cef5d20242b87f50337f1 on main.
coverage: 99.065% (-0.6%) from 99.683%
when pulling d9303ad9cc56a5bf523c82b5140fb04b07a1d840 on consistent-preference-name
into 9d7dc9004c2de42cda7d930108914dd8175b082b on main.
coverage: 99.688% (+0.005%) from 99.683%
when pulling 10dc14329d0fe3821d266bb0f3c624e2859a4794 on consistent-preference-name
into 9d7dc9004c2de42cda7d930108914dd8175b082b on main.
coverage: 100.0% (+0.3%) from 99.683%
when pulling 410ab8e4aeba59eb293b7de03f02afd9e6956bab on consistent-preference-name
into 9d7dc9004c2de42cda7d930108914dd8175b082b on main.
Very soft deprecation – just want the new name to show up on the README/docs. Probably won't even give a warning message for this change for a while (if ever).
Also adds a test of Preferences.jl by injecting custom versions of the key functions. Still not as good as an actual test of the
set_preferences!
interface, but still gives it a chance to walk through all the logic.