BUG: Problem with long board names

[byq77]

The board tiles don't fit in the BoardSidebar when some boards have long names.

[tu2-atmanand]

I have provided a small fix using CSS text-wrap: auto; property in the release 1.8.6.

Let me know if a better solution is possible.

[byq77]

I noticed, that you store both tasks.json and data.json files in the main branch. Aren't they supposed to be user's config files that are created by the plugin inside the plugin directory? Not to mention, both of them are marked in .gitignore. It makes contributing problematic, especially if you use the approach of checking out the repo inside the .obsidian/plugins.

git rm --cached tasks.json data.json

I think the latest release broke something again

[tu2-atmanand]

Yeah, I should have removed it a long back. But, you are right for other developers pulling out my changes from main branch it is actually an issue. Thank you for pointing that out.

I was actually keeping them in git because, its simply helping me understand what part of the file has been changed easily. For now I have removed these files from the main branch.

For the disappearing issue, I think its again something related to mostly either DEV environment and if its not, then probably after re-scanning the vault, it should be fixed or something. Hope it didnt re-appeared again as I tested it and havent faced it.

But if this issue did came back, I might have to try the one approach I mentioned in this comment : #583 (comment).

[byq77]

Interistingly, I deleted the plugin in my test vault and installed the latest release using BRAT and this time I did't encounter this issue. Maybe this is a problem with the dev environment. Base on https://github.com/tu2-atmanand/Task-Board/blob/bf593b5f6b6df10717debc41cc372d88f926a27d/.github/workflows/release.yml I've been using Node.js v18. I am new to Node.js development, and now I'm learning that v18 is a little bit dated..., should I use v24 LTS for dev?

[byq77]

Anyway, 1.8.6 fixes the issue with the long board names.

[tu2-atmanand]

I've been using Node.js v18. I am new to Node.js development, and now I'm learning that v18 is a little bit dated..., should I use v24 LTS for dev?

You might be right here. Although Node always keeps a backward compatibility, so nothing should break as such. But, I think I recently updated the packages of the project to use the latest. Here you may see I have updated the typing to version 24.0.14 and higher. :

Task-Board/package.json

Lines 20 to 21 in bf593b5

	"@types/node": "^24.0.14",
	"@types/react": "^19.1.8",

But in my local machine I am using a little older version of the package itself. And when this plugin builds in the GitHub Actions (which is in GitHub cloud) it fetches the latest packages.

Also, I am not expert in NodeJs yet, but I think node library and React library are sometimes coupled, so their version compatibility should be also maintained.

I am also using a little older versions, and the reason why I havent updated the packages in my local machine is simply because, I scare that something will break and then I will need to spend hours in setting up my environment again (also I am little lazy) :

>  node --version       
v22.17.1

> npm --version 
11.4.2

[byq77]

As I mentioned somewhere else, I recommend learning to use Docker and devcontainers. I literally spent maybe a minute setting up a dev environment in Visual Studio Code. I used some default JS+.TS image maintained by MS.