Forum Discussion
sergi
12 years agoContributor
To anyone interested, we've recently started using JSDoc 3 to document our Test Complete projects.
We also faced the very same issues everyone is describing here (basically the extension and text encoding).
We found a solution that works without having to change anything in the original Test complete .sj files.
It's just a matter of changing the JSDoc config file.
We use it this way (I've omitted the parts not related to solving the problems I mentioned before):
{
"source": {
"includePattern": ".+\\.sj?$"
},
"opts": {
"encoding": "utf16",
}
}
The encoding problem can also be solved by using "-e utf16" in the command line.
Please add my vote also to the DB.
We also faced the very same issues everyone is describing here (basically the extension and text encoding).
We found a solution that works without having to change anything in the original Test complete .sj files.
It's just a matter of changing the JSDoc config file.
We use it this way (I've omitted the parts not related to solving the problems I mentioned before):
{
"source": {
"includePattern": ".+\\.sj?$"
},
"opts": {
"encoding": "utf16",
}
}
The encoding problem can also be solved by using "-e utf16" in the command line.
Please add my vote also to the DB.