-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About unfolding the CATEGORIES #61
Comments
Fine with adding more categories to properties and special attributes, the more fine grained categorization actually already exists. The proposal on "class" doesn't make much sense to me, because right now we only show classes' names, and it's not clear what "private" and "public" means. |
Thanks for the reply, and let me explain myself clearer:
|
I'm generally ok with supporting 1, though I anticipate the change to be non-trivial, and I may not have enough time to work on it at this moment. for 2, I'd hold it. It is true that there's convention to treat the |
Cool, I get your point with the prefix matter. You're right about the changes this unfolding/indenting might've brought, I'll come up with more details to sort out what needs to be done. |
Proposal(more like a feature request)
Current categories make the result of
pdir()
a bit confusing, at least for myself. The originaldir()
doesn't have the problem since it outputs a simple alphabetized list, which is whypdir()
could do much better.An idea of mine is to extend categories as different levels, and keep them orthogonal at each level. For example:
The text was updated successfully, but these errors were encountered: