rfcs icon indicating copy to clipboard operation
rfcs copied to clipboard

project config location and lookup process

Open dherman opened this issue 6 years ago • 2 comments

It's come up in some discussions that we might want to consider putting Notion config information in a separate config file (e.g. my_project/.notionrc or maybe my_project/.config/notion/config), and nudge projects towards putting that file in their .npmignore, possibly by automating the workflow of configuring Notion through notion commands, like notion init.

I'll try to capture the constraints in this comment (and edit them if/when we identify more in discussion).

Constraints

  • Should libraries' config go into the npm registry?
  • What should the mental model be when you cd into my_project/node_modules/some_dependency?
  • What is the adoption overhead of the config strategy?
  • What behavior makes sense in large monorepos?

dherman avatar May 31 '18 17:05 dherman