Automattic / Automattic/VIP-Coding-Standards
Evaluate WPCS VIP issues
- Lingua principale
- PHP
- Stelle
- 261
- Fork
- 44
- Merge medio
- 19m
- PR unite (30g)
- 1
Descrizione
As part of [WPCS's reorganisation of labels](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1454), the `Component: VIP` is being removed, since WPCS `master` no longer contains the VIP category of sniffs.
The following Issues were still open at the time the label was removed, so these need checking to see if they still apply to any code that we now have in VIPCS:
- [x] ~https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1379~
- [x] ~https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/662~
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/661 (Applicable to WPCS)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/461 (Applicable to WPCS)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/462 (Possibly applicable to WPCS)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/74 (Possibly applicable to WPCS)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/91 (Valid for VIPCS, but not easily sniffable)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/80 (Valid for VIPCS, but not easily sniffable)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/295 (Likely valid for VIPCS)
- [ ] https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/475 (Likely valid for VIPCS)
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia leggendo l’issue 1454 collegata sulla riorganizzazione di WPCS, quindi esamina le dieci issue aperte elencate qui, in particolare 661, 461, 462, 74, 91, 80, 295 e 475. Confronta ogni issue con l’ambito attuale di VIPCS e WPCS; il lavoro è completato quando si registra se è ancora applicabile e si identifica qualsiasi attività di follow-up necessaria.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- php
- Ambito
- tooling
- Tipo di issue
- Refactoring
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 30/100