Alex
I ran eslint with --fix and re-added the noble-adapter file. For documentation, I experimented with two styles: an "Events" category in the description of every class, and a Markdown table...
> I think tying the events to the class directly makes it more readable and discoverable. It's not a strong preference though! I added an "Events" category to every class....
I was never using Pulsar as a project editor; only a text editor. Mostly I had files open in my Downloads folder, but I may have had some files open...
There's nothing that triggers the CPU usage. It happens as soon as Pulsar starts, even if no files are open.
Sure. I'll extract included services and power state from this and leave it as just capabilities.
I stand corrected: I leave this PR as included services and extracted capabilities and power state to separate PRs.
@kdewald any updates?