Skip to content
This repository was archived by the owner on Oct 1, 2020. It is now read-only.
This repository was archived by the owner on Oct 1, 2020. It is now read-only.

Is this project dead / unmaintained? #71

Open

Description

@tlhunter

This plugin in its current form leaves much to be desired. There are many unaddressed Issues/PR's. The broken, multiline output (#11) renders this plugin almost unusable.

Is this project dead? Are there any plans to pass ownership to either pass ownership to someone else or bless someone’s fork?

Activity

  1. gabelevi commented on Dec 13, 2017

    @gabelevi
    Contributor

    AFAIK there isn't anyone actively working on this at the moment. I do occasionally show up to merge PRs. If you or anyone else is interested in helping to maintain this project, that would definitely be appreciated 😄

    I haven't really looked into it recently, but probably a way forward is to focus on vim plugins that integrate with https://github.com/flowtype/flow-language-server. After googling, I found this wiki page which might help, but I haven't tried it myself: https://github.com/prabirshrestha/vim-lsp/wiki/Servers-Flow

  2. TrySound commented on Dec 13, 2017

    @TrySound

    @gabelevi I just tried. It's really nice and fast. However "hover" command doesn't seem work.

  3. dhilst commented on Mar 26, 2018

    @dhilst

    Can't get this working, as workaround I just let &makeprg = "yarn flow" and use quickfix to jump to errors. But now all errors are handled.

  4. ezmiller commented on Aug 31, 2018

    @ezmiller

    If this project isn't being maintained, are there other more active vim plugins for working with flow?

  5. h-michael commented on Sep 1, 2018

    @h-michael

    @ezmiller
    I recommend you use LanguageClient-neovim or some other lsp plugins if you use flow version 0.69.0 or above.

  6. TrySound commented on Sep 1, 2018

    @TrySound

    @h-michael Do you know how to configure LanguageClient-neovim to work with flow? Especially I'm interested in using locally installed version.

  7. h-michael commented on Sep 3, 2018

    @h-michael
  8. TrySound commented on Sep 3, 2018

    @TrySound

    @h-michael Sorry, it's probably a private project. I cannot access it.

  9. h-michael commented on Sep 3, 2018

    @h-michael

    @TrySound Sorry. Let it public.

  10. JESii commented on May 19, 2019

    @JESii
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions