Skip to content

[Feature]: Add formatter to the codebase #24

Description

@benjavicente

Checklist

  • I have searched the existing issues and have not found a duplicate
  • I have read the README and documentation
  • I agree to follow the OpenNG Foundation Code of Conduct

Problem

Not having a formater generates 2 small annoyances in code contribution:

  1. Line diffs could be larger that they should be thanks to different formatting
  2. Editors are usually setup with format-on-save, so contributors need to disable that to avoid the first point

Proposed solution

Add formatter. Prettier seems like the best candidate

Proposed API or usage

Alternatives considered

oxlint can't be used with the new Angular file naming convention

How important is this feature to you?

Nice to have

Contribution

  • I am willing to open a pull request for this feature

Additional context

We need to decide:

  1. What the config should be, and if we should override some configs depending on the directory
  2. If formatting should be part of CI checks

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions