Assigning loose "unknown" files to a project and disabling unknown category?

[gingerbeardman]

At times I seem to open up single files from within projects, and these are sorted as "unknown"

But a regex of the file path is enough to assign the project.

It's odd to see these loose files as "unknown" because there is a matching project.

eg.
/Users/matt/Projects/Playdate/sharkturtle/Source/main.lua
should be part of
sharkturtle

Is there any way I can manually assign these?

Preferably with the web interface, or if command line is required I'd need step-by-step help. 🆘

There are a dozen or two of them I would really like to remap. But there are almost 2000 of them in total. 😱

After remapping the most important ones, I would want to disable the "unknown" category. Is this possible?

Thanks for a useful project.

[gingerbeardman]

On wakatime I can do this with custom rules, and they are applied to past coding activity.

https://wakatime.com/faq#custom-rules

(if) file (contains) sharkturtle (then change) project (to) sharkturtle

This might be a workaround for the tidy up, after which I can reimport all my data. I have to wait for 24 hours before testing this, as I already did an import today.

I notice custom rules in wakapi do not seem to offer the same options here.

[gingerbeardman]

Alternatively, another way would be the ability to ingest ~/.wakatime.cfg and apply projectmap settings retrospectively.

[muety]

Hi @gingerbeardman, if I understood it right, the project is labeled as unknown, but not the language, correct? But it only happens for certain file within the same project folder structure? That's weird, don't really have a good explanation for that 🤔.

Generally, a good practice is to place a .wakatime-project file (see here) inside your project.

In case Wakapi's current rules functionality is not sufficient, there is #607 to add support for regexes. I'll work on implementing that soon.

If it's only about a one-time change to your already existing data, you could either do another import as you suggested or, if you're using wakapi.dev, send me an e-mail and tell me what remappings to perform via some manual, one-off database queries.

Hope that helps.

[gingerbeardman]

screenshots of the data currently imported into wakapi.dev
(screenshot taken from my local self-hosted mirror)

all my custom rules only matched 10% of unknown files.

[muety]

Will have a deeper look at latest on the weekend!

all my custom rules only matched 10% of unknown files.

What do you mean by that?

[gingerbeardman]

i tried to assign these loose/unknown files by settings lots of custom rules at wakatime.

even with dozens of custom rules I was only able to match and clean up a small number of such files. so,

all this to say, it's not really a workable solution.

[muety]

Do you think #607 would help?

[gingerbeardman]

That would allow the same sort of tweaking as wakatime custom rules. It would help but it's not a solution for me as there are simply too many "unknown" files so I would be stuck setting regex for a long time!

And even then there would be a remainder of unknown files that are not part of any project, truly unknown files that i'm not interested in.

[muety]

[...] I would want to disable the "unknown" category. Is this possible?

That's not supported currently.

[gingerbeardman]

OK, have opened #619

[muety]

Will close this discussion, as there's nothing left to do (except for #619) at this point, I think?

[gingerbeardman]

OK. I would say #607 and #619 will provide adequate workarounds. Time will tell if they're enough!