prettier / prettier/plugin-pug

Add third option for pugClassNotation and pugIdNotation

Open
#167 5 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted type: feature request
Dominant language
TypeScript
Stars
208
Forks
49
Avg merge
4h 26m
Merged PRs (30d)
8

Description

This will be a follow-up of #36, because this third option will need a bit more refactoring and is not quite as easy to implement as the other two options.
To let users already benefit from the other two options, we will create a release before starting working on this third option.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #36 and the existing implementation of pugClassNotation and pugIdNotation in the plugin. Clarify the intended third option and its behavior before beginning, since this issue does not specify it. Review the planned release context and confirm the refactoring scope with maintainers; done means the new option is implemented and covered by the plugin's tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
pug, typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.