Hi,

Like many over the past week I’ve stumbled into land of Lemmy in the wake of APIgate over at Reddit.

I see from the GitHub page that contributions are welcome, but at present there is no guidance on contributing, are you happy for folks to raise PRs for anything, or are there certain things you’d like to avoid and/or prioritise?

I’d be interested in getting involved in the project where time permits, I work full time as an iOS dev so I don’t have a ton of free time but this seems like a good project to contribute too 🙂

  • lFenix@lemmy.mlEnglish
    81·
    1 year ago

    Hey! It’s great that you’re interested in working on Mlem; any help is appreciated.

    I didn’t have a chance to write contributing guidelines yet, but in a nutshell:

    If you want any ideas for what I need help with at the moment:

    • Replacing old navigation with NavigationStack
    • In this file, I need to replace the TextFields with a UIKit text field that can communicate the current cursor position to the parent view via a @Binding: https://github.com/buresdv/Mlem/blob/master/Mlem/Views/Tabs/Posts/Components/Post/Components/Community View/Post Item/Post Expanded.swift. The new text fields need to have the same look as the current one
    • There are two files that contain a SFSafariViewController used to display a page in in-app Safari. There’s currently a bug that causes the feed to reload when the SFSafariViewController gets presented, but only if the user is currently looking at comments of a post. It would be amazing if this bug was fixed

    I can give you more info/ideas on GitHub if you’d like 😊

    • lFenix@lemmy.mlEnglish
      6·
      1 year ago

      Oh, also, you can check out the kanban board for Mlem on GitHub: https://github.com/users/buresdv/projects/4/views/1

      Anything in the “ideas” and “bugs” column is free game and you can work on any of them. Just watch out, if I put something in the “in progress” column, I’m already working on it, so please don’t start working on the same thing so we don’t run into conflicts 😅

    • nkh@beehaw.orgOPEnglish
      4·
      1 year ago

      Great, thanks!

      I just experienced that last bug twice while tapping through to the links in the post 😅

      I’ll get the project pulled down later today and have a proper look around, if I get time to address anything I’ll open a PR for review.

      • lFenix@lemmy.mlEnglish
        3·
        1 year ago

        Thank you very much! Please tell me if you need any help with understanding the code. Jsut be warned, there are some parts that are almost a year and a half old from back when I was still a beginner, so excuse some weirdness 😆 I’m working hard on replacing the old code, but it takes time.