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

Add working support for EditorConfig #16

Closed
wants to merge 2 commits into from
Closed

Add working support for EditorConfig #16

wants to merge 2 commits into from

Conversation

JackWH
Copy link

@JackWH JackWH commented Aug 6, 2016

In PhpStorm (and presumably other editors too), the existing .editorconfig file was throwing an error in the IDE:

EditorConfig: "support/editorconfig // " is not a valid value for file ~/vendor/servo/fluidxml/.editorconfig

As such, I've copied the contents of the editorconfig file from the /support directory in to the root directory, and deleted the old file (which wasn't being read anyway, as it was not preceded with a .).

It should be in the root directory - this file does not get parsed, and the root file throws errors.
The existing contents of this file threw an error before, so I've taken the real .editorconfig file and moved it here to prevent errors being thrown.
@coveralls
Copy link

coveralls commented Aug 6, 2016

Coverage Status

Coverage remained the same at 99.815% when pulling 45a8dae on JackWH:master into d5cadee on servo-php:master.

@daniele-orlando
Copy link
Member

daniele-orlando commented Aug 8, 2016

On which OS are you working on?
The EditorConfig file to point to your editor to is /.editorconfig in the root of the project, not the one in /support. The former is a symbolic link to the latter.

@JackWH
Copy link
Author

JackWH commented Aug 8, 2016

Well that's weird...

I installed the package via Composer on OS X in to a Laravel installation. The .editorconfig file was not a symlink, just a plain text file.

I just tried reinstalling the repository and now it appears as a symlink. No idea what happened there, but false alarm!

In my haste to help out I didn't notice the original file was a symlink on GitHub, hence I deleted it in my pull request and had never realised.

@daniele-orlando
Copy link
Member

No problem. Anyway thanks for your help, I appreciate.

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

Successfully merging this pull request may close these issues.

3 participants