Prefer TypeScript?

[septs]

I think strongly typed code helps maintain.

[DerekNonGeneric]

Yes, absolutely. I am setting up each project individually right now to see what each one needs as far as @typescript-eslint is concerned then I plan on putting that in a shareable config so that we don't really have to think about it anymore w/ @openinf/eslint-config we can just install it and extend the preset. I also like to ship typings, but so far feel that tests might need to be written in JS to actually know what is going on behind the scenes w/o transpilers fooling around.

[septs]

suggest, create @openinf/eslint-plugin

like https://github.com/DimensionDev/eslint-plugin

pre-ruleset and customize rule set in one package

documentation: see https://eslint.org/docs/latest/developer-guide/working-with-plugins

[DerekNonGeneric]

You can also use scoped packages in the format of @/eslint-plugin- such as @jquery/eslint-plugin-jquery or even @/eslint-plugin such as @jquery/eslint-plugin.
— https://eslint.org/docs/latest/developer-guide/working-with-plugins

Do you think we should use @openinf/eslint-plugin for the name here or should we specify something else like @openinf/eslint-plugin-prettier to get that handled for all prettier projects?

[DerekNonGeneric]

The reason why that repo is named inf-toolset instead of just toolset is because I was planning to imitate the https://github.com/github/rubocop-github style of partially revealing closed-source via config:

This repository provides recommended RuboCop configuration and additional Cops for use on GitHub open source and internal Ruby projects.

I am certainly open to changing the name. In fact, I had already thought that if that sort of mentality might be an issue, we can put all these configs in another repo like https://github.com/openinf/openinf (the naming can also be changed, but check the description of the project).

[septs]

I think, this org need a specificion repo, save {package,repo} naming style specificion, etc other specification or standard.

[DerekNonGeneric]

Yeah, a place to document coding conventions/style guide is a pretty good idea. Much of what https://github.com/openinf/inf-toolset was supposed to do w/ lint rules was documenting the preferences, but not immediately sure what to name the repo:

• openinf/style-guides
• openinf/coding-conventions
• openinf/coding-standards
• openinf/specifications

Is there an idiomatic repo name (like the community health files' names) that we should be using for this?

[septs]

I recommend, openinf/standards

to be extreme, e.g: protocol {specification,design}, file format {specification,design}, metadata file format (https://w3c.github.io/w3c.json.html), etc

[DerekNonGeneric]

Yeah, the org metadata file could also be specified in that repo. Hmm…