Skip to content

Future of Project #53

Open
Open

Description

@kylef

I am not interested in maintaining this project anymore. I think the problems that I was trying to solve in PathKit should just be solved in the standard library for Swift. Often enough, I think you might just be better off when avoiding the complexity of introducing a dependency for such convience when you can use FileManager from Foundation.

If anyone is actively using PathKit, or wants to maintain it then please let me know in these comments.

Activity

  1. felix91gr commented on May 6, 2018

    @felix91gr
    Collaborator

    It's sad to see one of your projects go. But you have your reasons.

    If at any time you'd like to re-take it, count on me to test it on Linux :)

  2. yonaskolb commented on May 6, 2018

    @yonaskolb
    Contributor

    I'm using PathKit in a lot of my projects. I find it a great convenience over FileManager. I agree it would be great to have native support in the standard lib for paths, but who knows when that will happen.

    Fair enough if you don't want to maintain this anymore. I'd suggest adding a few of the contributors to the repo. I'm happy to be added as well and would fix anything broken, as I do use it.

  3. kevinrenskers commented on Oct 18, 2021

    @kevinrenskers

    I do use PathKit in my static site generator Saga, and have a PR open that adds Codable support. I'd be happy to be added as a contributor as well, and am really hoping that more people get access and can keep on maintaining this project going forward.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions