Per 2022-11-04 dev call, consider adding version to .idpnew file names.
For example, cas-protocol.xml.4.2.1.idpnew or cas-protocol.xml.idpnew.4.2.1
Suggestion is to prefix the .idpnew suffix with the version, so that editors (like Eclipse) can be configured to open all *.idpnew files using a preferred editor, although it might better and just as easy to configure editors to use *.idpnew.* as the file-to-editor association pattern.
Environment
None
Activity
Show:
Scott CantorApril 26, 2023 at 5:11 PM
Sigh, I forgot to strip the puncutation as I planned.
Scott CantorApril 26, 2023 at 4:58 PM
Done using a convention of idpnew-NNN so that sorting works properly. I think filtering based on the beginning of the extension is more natural than having to wildcard the beginning.
Scott CantorNovember 4, 2022 at 4:56 PM
I think this is probably a V5 change simply because it could break scripts and so on.
Scott CantorNovember 4, 2022 at 4:55 PM
Actually for sorting reasons I’m thinking that not separating the idpnew/idpsave from the version is better because then the full extension will sort together across versions.
(ls -lX will sort that way.)
It won’t matter for sorting which is first in the extension, so it’s just aesthetic.
Per 2022-11-04 dev call, consider adding version to .idpnew file names.
For example,
cas-protocol.xml.4.2.1.idpneworcas-protocol.xml.idpnew.4.2.1Suggestion is to prefix the .idpnew suffix with the version, so that editors (like Eclipse) can be configured to open all *.idpnew files using a preferred editor, although it might better and just as easy to configure editors to use *.idpnew.* as the file-to-editor association pattern.