When we have a method in the docs (ex: History), we show the class that it's a part of (ex: QCAlgorithm.History) in the text when we describe the method.
Actual Behavior
The docs currently only show the member/method name, not the class. It can be confusing for new members who aren't familiar. For instance, if someone was copy-pasting the code snippets from https://www.quantconnect.com/docs/v2/writing-algorithms/historical-data/history-requests into an Alpha model, they wouldn't work because they would need to replace self with algorithm.
Checklist
[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
Expected Behavior
History
), we show the class that it's a part of (ex:QCAlgorithm.History
) in the text when we describe the method.Actual Behavior
The docs currently only show the member/method name, not the class. It can be confusing for new members who aren't familiar. For instance, if someone was copy-pasting the code snippets from https://www.quantconnect.com/docs/v2/writing-algorithms/historical-data/history-requests into an Alpha model, they wouldn't work because they would need to replace
self
withalgorithm
.Checklist
master
branch