Uh oh!
There was an error while loading. Please reload this page.
- Added namespace - #159
Conversation
theshivamlko
commented
Jul 2, 2024
@alexrintt can u approve this , required in my project. I have done this locally |
alexcmgit
commented
Jul 2, 2024
@theshivamlko is your project an app? If so, add a git dependency to AlexBacich's fork: dependencies:
shared_storage:
git:
url: https://github.com/AlexBacich/shared-storageref: masterIf your project is another package I don't recommend depending on |
AlexBacich
commented
Jul 2, 2024
@alexrintt , are you going to abandon this one? It's quite useful and I think I'm not the only one using it. Unless there are better alternates. |
alexcmgit
commented
Jul 2, 2024
Yes, I'm not actively working on this package anymore.
There are, maybe. I'm not aware of any yet but SAF is a common use-case.
Actually I prefer you to use your own repository because you will be the one maintaining it, it's easier to manage this way (CI/CD, permissions, secrets, etc.). You can also replace the package name with a name of your choice and publish to pub.dev. If you agree with that, I will add a deprecation notice and a link redirecting to your repository. What do you think? |
AlexBacich
commented
Jul 2, 2024
@alexrintt , I think that's better option than simply abandoning. However, the most optimal one feels to me to keep just one project. You can add me in Package Ownership in And similar thing in the GitHub repository. This way we may maintain consistency in issues, commits history, etc. And no need to migrate from one package to another. |
@AlexBacich Fork it, publish your own, else I am doing it, there are so many duplicate packages already on pub.dev |
AlexBacich
commented
Jul 3, 2024
@theshivamlko , go for it. |
No description provided.