You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to identify all of the "new" or "since" members across the entire set of documentation. Is this possible?
For instance, the developer adds several new features to multiple classes. The person in charge of documentation maintenance would benefit from using JSDuck to see all "new" members across all of those classes to highlight them in a consolidated release notes text. We would prefer to rely on JSDuck to surface this information. This is opposed to 1) having the documentation maintaner navigate across all of the classes from the JSDuck output, manually noting the "new" items, or 2) using diffs of source code to identify this information.
The text was updated successfully, but these errors were encountered:
I actually implemented it in 4.x branch, merging it also to 5.x.
There's still some tweaking left to do and I had a release of 4.8.0 just yesterday. The 5.x branch on the other hand is in the middle of some larger changes. Maybe I'll do a 4.x release next week, but I'm quite unsure about 5.x line.
It would be useful to identify all of the "new" or "since" members across the entire set of documentation. Is this possible?
For instance, the developer adds several new features to multiple classes. The person in charge of documentation maintenance would benefit from using JSDuck to see all "new" members across all of those classes to highlight them in a consolidated release notes text. We would prefer to rely on JSDuck to surface this information. This is opposed to 1) having the documentation maintaner navigate across all of the classes from the JSDuck output, manually noting the "new" items, or 2) using diffs of source code to identify this information.
The text was updated successfully, but these errors were encountered: