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

What is the status of this repo? #14

Open
xuhdev opened this issue Jun 3, 2020 · 4 comments
Open

What is the status of this repo? #14

xuhdev opened this issue Jun 3, 2020 · 4 comments

Comments

@xuhdev
Copy link
Member

xuhdev commented Jun 3, 2020

I'm very confused. The repo doesn't state how it should be used.

@xuhdev
Copy link
Member Author

xuhdev commented Jun 3, 2020

ping @ffes Do you think we need to add something to README?

@ffes
Copy link
Member

ffes commented Jun 3, 2020

You're right. At the moment it is not clear. I personally think it could become a useful source for plugin authors to add snippets to a .editorconfig file, among others. I'm sure others have much better ideas to utilize the data.

But at the moment there are not much defaults in the list and the file format is not finalized as well.

And thanks for the ping. I more or less forgot about this repo.

@xuhdev
Copy link
Member Author

xuhdev commented Jun 3, 2020

Actually someone asked something related to this repo in the mailing list: https://groups.google.com/d/msg/editorconfig/0QOiB3DjUl4/pl2AJAOdBQAJ

@ffes
Copy link
Member

ffes commented Jun 5, 2020

Do you think we need to add something to README?

Yes! I bit clarification what the intent of the repo is, is surely a good thing to do. I will pickup #10 again to finalize the format. Maybe wait for that because the PR does include changes to the README.

Once that is done, it is just a matter of adding more snippets. And get the attention to plugin developers to include a snippet feature. For Notepad++ I will definitely look into that myself.

I also have some code lying around to include the content of editorconfig-defaults.json in the main website. This way the snippets will become more visible as well.

But as said, first resolve the conflict and finalize the format as I tried with #10

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