it-at-m / it-at-m/refarch

[Maintenance] Centralize prettier configuration

Open
#387 0 comments 0 reactions 0 assignees View on GitHub
Component: Tools Priority: Medium Type: Maintenance
Dominant language
Java
Stars
7
Forks
5
Avg merge
2d 4h
Merged PRs (30d)
34

Description

### Relevant component

refarch-tools

### Problem description (optional)

We already have `java-tools` so I suggest creating a new directory for `node-tools` and maintaining a package for the prettier configuration there.
Currently the prettier tooling is located in https://github.com/it-at-m/itm-prettier-codeformat, however I think it would be way more manageable if we could maintain all configurations in one place.

### Desired solution

Move content of https://github.com/it-at-m/itm-prettier-codeformat over to this repository and release under a new npm package name.
Also, set the old package to deprecated and link to the new one.

### Considered alternatives (optional)

_No response_

### Additional context (optional)

_No response_

### No duplicate

- [x] I confirm that this issue is not a duplicate

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the existing java-tools layout with the itm-prettier-codeformat repository linked in the issue. Define the new node-tools package around the migrated Prettier configuration, then verify that it can be released under a new npm name and that the old package points users to it and is deprecated.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
release, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.