Skip to content
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

Ability to hide unknown section #619

Closed
gingerbeardman opened this issue Mar 10, 2024 · 5 comments
Closed

Ability to hide unknown section #619

gingerbeardman opened this issue Mar 10, 2024 · 5 comments
Labels
effort:3 enhancement New feature or request prio a

Comments

@gingerbeardman
Copy link

unknown files are loose files that have been opened that are not recognised as part of any project.

I have almost 2000 of them.

from
#617 (comment)

@muety
Copy link
Owner

muety commented Mar 11, 2024

Note to myself: this would either require to pre-compute two different summaries, one with unknown projects included and one without them (heartbeat's project column being NULL or "") or be always computed on the fly (analogously to when applying filters), which would result in poor performance, though. As simple as it sounds, this is not as straightforward from a technical perspective.

@muety muety added enhancement New feature or request prio c effort:3 labels Mar 11, 2024
@muety
Copy link
Owner

muety commented Mar 12, 2024

Question related to this: would you only want to hide the unknown project from the list of projects (top left chart on the dashboard) or would you also want it to be excluded from the total duration and from the language-, editor-, etc. charts? The former would be trivial to implement, the latter is harder for the above reasons.

@gingerbeardman
Copy link
Author

Yeah, I ideally it would be excluded everywhere. It a thorn in my side, out of sight out of mind.

@muety
Copy link
Owner

muety commented Mar 14, 2024

Had another thought about this. If we made this a global per-user setting (which would require to re-compute all summaries once initially), implementing this would actually be quite straightforward. Could be implemented in a way similar to how #156 will be realized. Will look into this soon!

@muety muety added prio a and removed prio c labels Mar 14, 2024
@muety muety closed this as completed in 34961e7 Mar 29, 2024
@gingerbeardman
Copy link
Author

gingerbeardman commented Mar 31, 2024

Thanks so much, working a treat! My sanity is restored (somewhat) 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:3 enhancement New feature or request prio a
Projects
None yet
Development

No branches or pull requests

2 participants