Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[firebase_storage] Implement "listAll" function #232

Closed
wants to merge 27 commits into from

Conversation

danysz
Copy link

@danysz danysz commented Sep 28, 2019

Description

We implemented the "listAll" function for both Android and iOS.

Related Issues

#83

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (flutter analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
  • I updated CHANGELOG.md to add a description of the change.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
  • No, this is not a breaking change.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@danysz
Copy link
Author

danysz commented Sep 28, 2019

@googlebot I fixed it.

@googlebot
Copy link

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@emildesign
Copy link

@googlebot I consent.

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@danysz
Copy link
Author

danysz commented Sep 28, 2019

I really think that some "settings" for the format which can be imported directly in Android Studio and in Xcode should be provided so the "format" will be made automatically without changing the "Default" which is coming inside.

@wladosh
Copy link

wladosh commented Jun 4, 2020

Is this waiting for a web implementation? or is there something else holding this back?

soon will be a year since I made it and they don't have time to review it. I got in contact with @collinjackson about it (he is the now who made the first review) but it looks that the other guy is just careless about what is going on and nobody cares about the developers.
I stopped updating firebase and other open sources since nobody is doing anything about it.
You can point to my repository and use it.

BTW, since I made it because a lot of changes there are now conflicts.

enjoy

that's really sad you did good work and I really need this in my project...

@conleec
Copy link

conleec commented Jun 8, 2020

Sigh...
That is sad...

@kormemis
Copy link

.listAll() function returns as Future , how could I convert it as ListResult ?
thanks.

@Ehesp
Copy link
Member

Ehesp commented Jun 10, 2020

Hi All - Storage is on the list to be sorted as part of #2582 and this will be addressed.

Thanks for the work that's been put in. As we're working on updating the tests & CI flow for each plugin, I think it'd be best if we hold of merging this one since it bumps the underlying native SDK versions. Without proper tests in place, it may well break functionality of other plugins/features.

@danysz
Copy link
Author

danysz commented Jun 10, 2020

Hi All - Storage is on the list to be sorted as part of #2582 and this will be addressed.

Thanks for the work that's been put in. As we're working on updating the tests & CI flow for each plugin, I think it'd be best if we hold of merging this one since it bumps the underlying native SDK versions. Without proper tests in place, it may well break functionality of other plugins/features.

Thanks...when I made it first everything was update and everything was possible to be merged automatically, but it was looooong time ago.

@abhirakshit
Copy link

Any ETA on when this might make to release please?

@Harishwarrior
Copy link

Harishwarrior commented Jul 7, 2020

This is the important feature used by almost every firebase user. Any ETA on the plugin update?. If this will take too long then i will switch to java. That's why am asking.

@mirkelor
Copy link

Please review this pr.

@Harishwarrior
Copy link

Hi All - Storage is on the list to be sorted as part of #2582 and this will be addressed.

Thanks for the work that's been put in. As we're working on updating the tests & CI flow for each plugin, I think it'd be best if we hold of merging this one since it bumps the underlying native SDK versions. Without proper tests in place, it may well break functionality of other plugins/features.

Thanks...when I made it first everything was update and everything was possible to be merged automatically, but it was looooong time ago.

Can you update it now?

@danysz
Copy link
Author

danysz commented Aug 6, 2020

Hi All - Storage is on the list to be sorted as part of #2582 and this will be addressed.
Thanks for the work that's been put in. As we're working on updating the tests & CI flow for each plugin, I think it'd be best if we hold of merging this one since it bumps the underlying native SDK versions. Without proper tests in place, it may well break functionality of other plugins/features.

Thanks...when I made it first everything was update and everything was possible to be merged automatically, but it was looooong time ago.

Can you update it now?

What for ? It doesn't looks that someone really cares about us.

@Harishwarrior
Copy link

Harishwarrior commented Aug 6, 2020

@danysz I don't know why they didn't merge this yet. But, your work is really great. Don't let that fade away. Almost 25 guys I know alone, using this feature.

Edit: and what I meant by update is to resolve the merge conflicts.

@danysz
Copy link
Author

danysz commented Aug 6, 2020

@danysz I don't know why they didn't merge this yet. But, your work is really great. Don't let that fade away. Almost 25 guys I know alone, using this feature.

I know at least same amount if not double. Some of them even wrote me, but after almost a year waiting and trying actively to get in touch with @collinjackson and others which didn't do anything about it I am just really disappointed.

Copy link

@tgbarker tgbarker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing semicolon at end of line 333 plugins/firebase/storage/FirebaseStoragePlugin.java, does not compile.
Thank you for this feature, I still use your branch and noticed it didnt compile this morning.

@Ehesp
Copy link
Member

Ehesp commented Aug 6, 2020

This will be added as part of the #2582 rework - it overhauls the API and converts it to a federated setup so we were unable to use this PR. Hopefully the updated work should be landing in a couple of weeks.

@PhamQuocHuy98

This comment has been minimized.

@Maadhav
Copy link

Maadhav commented Aug 20, 2020

Any update on this? Is this available in the latest version?

@gaetschwartz
Copy link

@Maadhav Nope it is not available in the latest version... I wonder if they will merge it someday ?

@Ehesp
Copy link
Member

Ehesp commented Aug 20, 2020

@blaxou https://github.com/invertase/flutterfire/pull/53

@gaetschwartz
Copy link

@Ehesp Alright, why do you use two different repositories ? It makes things a lot more confusing for users and issues etc. Also don't hesitate to communicate on in this PR if you work on it, as you probably noticed a lot of people want this feature so let's reassure them !

@Ehesp
Copy link
Member

Ehesp commented Aug 20, 2020

@blaxou It allows us to focus on big upgrades without noise from the main one. Once it's up to standard we'll merge them in.

@Salakar Salakar mentioned this pull request Sep 22, 2020
22 tasks
@Levi-Lesches
Copy link
Contributor

Not to snoop, but https://github.com/invertase/flutterfire/pull/53 has been merged! Seems to be only a matter of time until it's merged into this repo

@Levi-Lesches
Copy link
Contributor

Follow #3612 for progress

@Salakar
Copy link
Member

Salakar commented Sep 22, 2020

Hey all, as @Levi-Lesches mentioned above, our rework PR is up at #3612 and is now going through dev release cycles. A firebase_storage dev release is now available (5.0.0-dev.1) with all the changes in that PR including the listing API - please could you try it out and provide feedback on the #3612 PR :)

Thanks for sending up this PR though @danysz - really appreciate it, sorry it didn't get the attention it deserved. Given that it's now implemented in the other PR I'm going to go ahead and close this PR.

@Salakar Salakar closed this Sep 22, 2020
Ehesp pushed a commit that referenced this pull request Oct 6, 2020
@firebase firebase locked and limited conversation to collaborators Oct 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.