Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lobby for .config/ #2

Open
15 of 54 tasks
shannonmoeller opened this issue May 4, 2015 · 2 comments
Open
15 of 54 tasks

Lobby for .config/ #2

shannonmoeller opened this issue May 4, 2015 · 2 comments

Comments

@shannonmoeller
Copy link
Owner

Responses from maintainers to requests for optional .config/ support varied widely. Some plan to implement, others won't implement but were supportive of the idea, others slammed the door entirely. Among the more supportive responses was the recommendation for publishing a module that implements the requested logic followed by pull requests.

This module is the brain child of those conversations and will be used as a base for submitting PRs. Eventually it will be updated to either use or establish a pattern for using findup-sync to locate configs. This issue will track the progress of PR implementations and their acceptance or rejection.

  • npm (rejected)
  • jspm (accepted)

  • bower
    • Feature requested. (open)
    • Fork
    • PR
  • eslint
    • Feature requested. (rejected, unsupportive)
    • Fork
    • PR
  • findup
    • Feature requested. (open)
    • Fork
    • PR
  • findup-sync
    • Feature requested. (rejected, supportive)
    • Fork
    • PR
  • grunt
    • Feature requested. (open)
    • Fork
    • PR
  • gulp
    • Feature requested. (rejected, mildly supportive)
    • Fork
    • PR
  • karma
    • Feature requested. (open, supportive)
    • Fork
    • PR
  • liftoff
    • Feature requested. (open)
    • Fork
    • PR
  • jscs
    • Feature requested. (open)
    • Fork
    • PR
  • jshint
    • Feature requested. (open, mild support)
    • Fork
    • PR
  • travis-ci
    • Feature requested. (open)
    • Fork
    • PR
  • yo
    • Feature requested. (rejected, supportive)
    • Fork
    • PR
  • zuul
    • Feature requested. (rejected, mildly supportive)
    • Fork
    • PR
@shannonmoeller
Copy link
Owner Author

shannonmoeller commented Jul 11, 2020

Another attempt at championing this idea: nodejs/tooling#79

@ssbarnea
Copy link

How about teaming-up with this challenge? Getting the first test of tools to to adopt it would be the hardest and we need to start with less mainstream ones. Check https://dot-config.github.io/ -- the first 10 would be the hardest.

I a little bit disappointed of general view on this from other which do seem to want to use the root level to advertise the tool use, at detriment of developer experience. Moving stuff to .config is seen as reducing the visibility. Probably none will confess that but it is there.

I would even say that it would be a bad idea to aim too high before we have few smaller projects adopting it. A bottom-up approach seems better in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants