Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

Document infrastructure and behavior of the printer #2550

Closed
Tracked by #2403
ematipico opened this issue May 6, 2022 · 4 comments
Closed
Tracked by #2403

Document infrastructure and behavior of the printer #2550

ematipico opened this issue May 6, 2022 · 4 comments
Assignees
Labels
A-Documentation Area: documentation A-Formatter Area: formatter I-Staff Implementation: should be in charge of a core member of the team

Comments

@ematipico
Copy link
Contributor

ematipico commented May 6, 2022

As agreed during our last standup, I created this is to track and improve our internal documentation of our printer

@ematipico ematipico added A-Documentation Area: documentation A-Formatter Area: formatter I-Staff Implementation: should be in charge of a core member of the team labels May 6, 2022
@yassere yassere added this to Rome 2022 May 8, 2022
@yassere
Copy link
Contributor

yassere commented May 11, 2022

This is on hold for now because we’re considering rewriting the printer to make its behavior more closely match Prettier.

@MichaReiser
Copy link
Contributor

See #2579 for the work around getting Rome closer to Prettier.

@MichaReiser
Copy link
Contributor

@ematipico are you looking for a more extensive documentation than what's exposed in the API documentation

@ematipico
Copy link
Contributor Author

I think we did a good job :) happy to close it

@ematipico ematipico moved this to Done in Rome 2022 Oct 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Documentation Area: documentation A-Formatter Area: formatter I-Staff Implementation: should be in charge of a core member of the team
Projects
Status: Done
Development

No branches or pull requests

3 participants