If the id is "topic+XYZ" then in the same manual there are two alias that are the same (like as.brobmat in Brobdingnag man/brobmat.Rd). It would be ideal to make use unique(topic) or similar when creating the topics (we didn't identify where this is needed).
This could also be checked at R CMD check.
For others like "MixNRMI2_+3Akappa" presumably from AdvBinomApps we don't know where the issue is from.
In others, like in the BuildSys the S4 object initProjectFromFolder is documented to have "DEFINES" and "defines", which are then converted to lowercase which leads to duplicated ids (other example is package Bayesiangammareg with Bayesiangammareg function having bpri and Bpri).
The easy solution is to add the number of the argument they are. Instead of object/function+levellowercaseArgment it could just use numbered arguments: object/function+level_numberArgument_lowercaseArgument.
Long term solution would be to check for duplicated arguments names with different case (NOTE?). I think this can lead to misleading users at makes it harder to understand the functions.
If the id is "topic+XYZ" then in the same manual there are two alias that are the same (like as.brobmat in Brobdingnag man/brobmat.Rd). It would be ideal to make use
unique(topic)
or similar when creating the topics (we didn't identify where this is needed). This could also be checked atR CMD check
.For others like "MixNRMI2_+3Akappa" presumably from AdvBinomApps we don't know where the issue is from. In others, like in the BuildSys the S4 object initProjectFromFolder is documented to have "DEFINES" and "defines", which are then converted to lowercase which leads to duplicated ids (other example is package Bayesiangammareg with Bayesiangammareg function having bpri and Bpri). The easy solution is to add the number of the argument they are. Instead of object/function+levellowercaseArgment it could just use numbered arguments: object/function+level_numberArgument_lowercaseArgument.
Long term solution would be to check for duplicated arguments names with different case (NOTE?). I think this can lead to misleading users at makes it harder to understand the functions.