prettier/prettier-atom

Watch .prettierrc for changes and reload without cache if so

Open

#270 opened on Sep 15, 2017

View on GitHub
 (13 comments) (10 reactions) (1 assignee)JavaScript (764 stars) (106 forks)batch import
enhancementhelp wanted

Description

If I change any configuration in my .prettierrc file after atom having been opened, the changes don't seem to be applied.

Is this intended? It seems the config is cached when atom launches and then it uses this one the whole time the editor is opened, meaning if I make a change to the config I need to restart atom.

It wasn't so intuitive to me initially and I would have thought it would lookup the .prettierrc config everytime it formats to make sure it's using the right config.

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptAtom package development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate how prettier atom currently caches .prettierrc config. Look at the configuration loading code (likely in lib/config.js). Consider using Atom's file watcher API or Node's fs.watch to monitor .prettierrc for changes. When a change is detected, reload the config without restarting Atom. Ensure the existing formatting behavior is preserved.