Add support for Alfred 4 or newer

[LitoMore]

Resolves #23

[SamVerschueren]

Hi @LitoMore, thanks for the PR!

Just upgrading the package doesn't work, because it now returns an object instead of a string. For example, this line should be changed to something like this.

const getWorkflowDir = () => resolveAlfredPrefs().then(prefs => path.join(prefs.path, 'workflows'));

Same goes for the other resolveAlfredPrefs() calls

[LitoMore]

Just upgrading the package doesn't work, because it now returns an object instead of a string.

Thanks! Updated!

[SamVerschueren]

I'm going through all the files and noticed that the unlink functionality is probably broken as well because it's hardcoded for Alfred 3. Not sure what the paths are for Alfred 4 and above?

https://github.com/SamVerschueren/alfred-link/blob/master/lib/unlink.js#L17-L22

[kouchao]

@SamVerschueren

/Library/Application Support/Alfred/Workflow Data


/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data

[LitoMore]

@kouchao Thank you.

I think we should only unlink the version returns by the resolveAlfredPrefs. I'm writing the logic for unlink, will be updated soon.

[LitoMore]

@SamVerschueren Updated.

I also added a section Supporting Versions to readme.

[SamVerschueren]

It's coming together :). Last comments that needs to be resolved and I believe that should be it 👌

[SamVerschueren]

Awesome! Thank you very much @LitoMore! 🎉

[LitoMore]

@SamVerschueren You are welcome. Next step I am going to create a pull request on Alfy.

[SamVerschueren]

No need, semver catches this because I released it as patch. Tested it locally and works perfectly fine for me.

Had to do a quick fix here though SamVerschueren/resolve-alfred-prefs@2072c5b. Suddenly your user home path came up in my terminal 😂

[LitoMore]

No need, semver catches this because I released it as patch. Tested it locally and works perfectly fine for me.

Good point.

Had to do a quick fix here though SamVerschueren/resolve-alfred-prefs@2072c5b. Suddenly your user home path came up in my terminal 😂

OK, let me create a PR to fix this bug.