any reason why you changed this setting?

Do you remember that I had an issue on CI step.?

Now it has the same as master branch:
https://github.com/BoostIO/Boostnote/blob/master/.prettierrc

{
  "singleQuote": true,
  "semi": false,
  "jsxSingleQuote": true
}

ah okay

This method online call one method, why can't we directly call checkWakatimePluginRequirement?

I was thinking on this page is named plugins so on future new user could use this function to check if their developed plugins has all requirements. But I will remove it.

The last 3 variable is all booleans. I suggest we change to object type for more clarification. For example, if we change this function to:

function sendWakatimeHeartBeat(storagePath, noteKey, storageName, {isWrite, hasFileChanges, isFileChange}) {
  ...
}

We can keep the code inside the same but when we call this function, we will call it like this:

sendWakatimeHeartBeat(
  storagePath,
  noteKey,
  storageName,
  { isWrite: true, hasFileChanges: false, isFileChange: true}
)

This part seem to be a bit repeative. Surely we can improve the quality of this code by doing something similar to this:

if (this.props.onChange) {
    this.props.onChange(editor)
}

const isWrite = !!this.props.onChange;
const hasFileChanges = isWrite;

if (storage) {
  sendWakatimeHeartBeat(
    storage.path,
    noteKey,
    storage.name,
    isWrite,
    hasFileChanges,
    false
  )
}

DONE, It was very old code XD

This is wrong command name 😄 Should be like this:

Done

I think Wakatime isn't the only plugin that we support so it's better to create a section for Wakatime in this plugin setting page. Just a simple section with title Wakatime and bellow is a check box saying enable wakatime? and below it is the text box for wakatime key. If we plan to only have 1 plugin then this plugin page should change the name to Wakatime which I think will be worst cus harder to change when we want to support more plugins

Done 👍