Fix: Don't link to undocumented types in API docs#14878
Fix: Don't link to undocumented types in API docs#14878straight-shoota merged 2 commits intocrystal-lang:masterfrom
Conversation
Co-authored-by: Sijawusz Pur Rahnama <sija@sija.pl>
|
Maybe it would make more sense to pass |
Why? What would that improve? If they're instance methods on |
To make it clear in the html template from where the types are fetched, but maybe one should understand that from the context. |
|
I see. Maybe it could make sense to move the |
There was a problem hiding this comment.
I understand @Sija's feeling: I liked the type.subclasses notation that was a little more explicit (i.e. I want the subclasses of type). We can't do that because we need types from the template, and filtering in the template sounds like the correct place... so what about a filter method, for example with_docs(type.subclasses)?
Now this is nitpicking and the PR can be merged as-is 👍
|
I noticed while looking into the latest comment on #12018, that this PR may have changed more than we expected? The I can move this to its own issue if this is indeed a regression. |
|
Yeah, that doesn't seem to work correctly. I believe |
This reverts commit 78c9282.
|
I believe the filtering must be done in |
|
This patch was eventually reverted in #14908 due to #14878 (comment) |


Fixes #9816