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
Is your feature request related to a problem? Please describe.
While working with various codebase that rely on different diffuser versions I find it challenging to pinpoint when a given sheduler/ base model was introduced.
For now I basically manually increment the version in the URL at a given doc page -> ctrl + F and repeat until I find it.
Describe the solution you'd like.
Add a notice next to classes in the doc reference pages like introduced in 0.24
Describe alternatives you've considered.
A single dedicated page with a big filterable table providing this kind of data
The text was updated successfully, but these errors were encountered:
An easier way to help you differentiate the versions, is to navigate to the source file of the class on Github and hit the "history" tab. Or, you can use the "Blame" button if your file contains multiple classes.
I do agree with the suggestion though; would be nice to have in the docs but probably tricky to do retroactively.
Is your feature request related to a problem? Please describe.
While working with various codebase that rely on different diffuser versions I find it challenging to pinpoint when a given sheduler/ base model was introduced.
For now I basically manually increment the version in the URL at a given doc page -> ctrl + F and repeat until I find it.
Describe the solution you'd like.
Add a notice next to classes in the doc reference pages like introduced in 0.24
Describe alternatives you've considered.
A single dedicated page with a big filterable table providing this kind of data
The text was updated successfully, but these errors were encountered: