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

[Core] Plugin doesn't seem to work on Atom 1.12.6 #27

Open
Hesediel opened this issue Dec 5, 2016 · 4 comments
Open

[Core] Plugin doesn't seem to work on Atom 1.12.6 #27

Hesediel opened this issue Dec 5, 2016 · 4 comments
Labels

Comments

@Hesediel
Copy link

Hesediel commented Dec 5, 2016

Hi,

Discovering your plugin today, I've :

  • Installed Atom 1.12.6 on my computer (Windows 7).
  • Used "File > Add a Project Folder..." in order to put on Atom folders containing features files.
    I've ordered my folder like this : "Root > features > MyFirstFeature", the last folder containing a bunch of feature files.
    When I open one of those files, nothing happens, neither syntax highlight nor autocompletion when I write any keyword (as Given, When, Then).

Could you please advise ?

Regards.

@mickael28
Copy link

It doesn't work for me with the latest Atom 1.12.7 as well.

Although the error I'm getting is:
cucumber-autocomplete: Cannot find features directory at C:\Users\admin.atom/features. Please update your setting to point to the location of your features directory.

I've tried with relative path, full path, etc and it's always failing. I'm not sure why the error message is concatenating C:\Users\admin.atom as part of the path?

@tomkadwill tomkadwill added the bug label Dec 13, 2016
@tomkadwill
Copy link
Owner

Thanks @Hesediel and @mickael28 for reporting. These both look like issues with Windows. I'll try to get a VM so that I can reproduce these issues and test. I'll try to do that by next week

Sorry for the late reply!

@scato
Copy link

scato commented Sep 7, 2017

For posterity, I just found out that this package won't work by itself. You need at least some package like language-gherkin installed as well.

What happens otherwise, is that Atom won't recognise the language, so the provider can't match using the selector .source.feature.

@tomkadwill
Copy link
Owner

@scato Thanks for reporting. I should probably add language-gherkin as a dependancy to prevent these types of bugs

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

No branches or pull requests

4 participants