This PR adds a facility where you can note that an action should no longer be used by adding the command:
setDeprecated("LESS_THAN");
In the registerKeywords method of an action. The deprecated actions are then tracked in the syntax.json file. By putting this information in that file this way we can note eggs and lessons that are using actions that we have moved on from at some stage in the future.
The first commit in this sequence fixes a regtest that appears to be broken on master. I am not sure where this regtest came from.
Target release
I would like my code to appear in release 2.11
Type of contribution
[x] changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
[ ] changes to a module not authored by you
[ ] new module contribution or edit of a module authored by you
Copyright
[x] I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.
[ ] the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.
Tests
[x] I added a new regtest or modified an existing regtest to validate my changes.
[x] I verified that all regtests are passed successfully on GitHub Actions.
Description
This PR adds a facility where you can note that an action should no longer be used by adding the command:
In the
registerKeywordsmethod of an action. The deprecated actions are then tracked in the syntax.json file. By putting this information in that file this way we can note eggs and lessons that are using actions that we have moved on from at some stage in the future.The first commit in this sequence fixes a regtest that appears to be broken on master. I am not sure where this regtest came from.
Target release
I would like my code to appear in release 2.11
Type of contribution
Copyright
COPYRIGHTfile with the correct license information. Code should be released under an open source license. I also used the commandcd src && ./header.sh mymodulenamein order to make sure the headers of the module are correct.Tests