Skip to content

Release/1.0.28 #460

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

Merged
merged 37 commits into from
Oct 11, 2020
Merged

Release/1.0.28 #460

merged 37 commits into from
Oct 11, 2020

Conversation

fischerscode
Copy link
Contributor

@fischerscode fischerscode commented Oct 2, 2020

TODO before merging:

TODO after merging:

  • create parse_server_sdk_flutter at pub.dev
  • create new development branch

Sorry, something went wrong.

phillwiggins and others added 23 commits August 28, 2020 08:38
- Update references to 1.0.28
* Replace devicelocale by Platform.localeName call

* Use flutter_test to meet new requirements
* make livequeries web implementation more similar to the mobile implementation

* combining both livequery implementations

* make livequery "part of flutter_parse_sdk"

* smal fix
* Set TODO's

Set TODO's, needed for #78 (comment)

* First step of seperating the flutter and the dart parts

* added one todo

* remove connectivity from the dart part

* Removed path_provider from the dart part

Not so happy with the fact that `CoreStoreSembastImp implements sdk.CoreStoreSembastImp` in `parse_server_sdk.dart` but I didn't find a better solution.

* Removed shared_preferences from the dart part

* Update pubspec.yaml

* Update parse_server_sdk_dart.dart

* removed dart:ui from dart part

* removed flutter from dart part

* fixed tests
* Add websupport for CoreStoreSembastImp

* Add debug warning when using sembast on web

ParseCoreData().debug should be null at that time

* fixed issues
If state is equal to ConnectivityResult.none, then there is no connection with LiveQuery server (for example when internet is disconnected). _setReconnect function will now retry connection.
ConnectivityResult to ParseConnectivityResult

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
* split code into package directories

* removed unused dependencies

* Updated READMEs

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
….0.28
* docs changes

* remove flutter_test

* CoreStore was implemented twice

* implemented CoreStoreMemoryImp (default corestore for dart)

* fix tests

* Update .travis.yml
* fix flutter logo

* fixed flutter link
Should work again.
* store password in field

Potential fix for #444

* remove password from clone
Added @BaranMichal25 fix for #456.
#456 (comment)
* LiveList: added preloadedColumns

* LiveList: fixed bug with lazyloading=false

* formatting

* Add README section for flutter
* Create migrate-1-0-28.md

* Update migrate-1-0-28.md

* Update migrate-1-0-28.md

* Update migrate-1-0-28.md

* Merge from upstream/release/1.0.28

* fix typos

* added "changed network library" to migration guide
@fischerscode
Copy link
Contributor Author

@phillwiggins
The README of the Flutter package is in pretty good shape. The Dart's one however is almost just a copy from the Flutter's one.
Should we publish 1.0.28 with the WIP README and without an example or should we delay the release and fix those issues first?
Personally, I have not used the dart package, yet (except in short tests).
And I think adding an example and a README makes sens as soon as the package has been used in a real project, in order to gain some experience and figure out some best practices.

* Merged manually from branch dio

* fixing nullpointer

* Fix batch operations

Maybe dio changes the toString behaviour.

* use mine

* keep content-type

* fix file upload issue

* fixed file uppload on web

* performance improvement in parse_file_web

* fix for issue #456 (#457)

Added @BaranMichal25 fix for #456.
#456 (comment)

* fix flutter test

* fix crash when debug=true

* fix dart test

* add ProgressCallback in README

* added progressCallback example
@fischerscode
Copy link
Contributor Author

change parse_server_sdk dependency to pub.dev (?)

Does anyone know if a relative path is allowed when publishing to pub.dev?

Added section for tests at migration guide.
Fix: #385 (comment)
* signup - use toJson

Co-Authored-By: itmesh <[email protected]>

* fix password update
@fischerscode fischerscode marked this pull request as ready for review October 9, 2020 14:37
@fischerscode
Copy link
Contributor Author

@phillwiggins
I think it's all ready. 👍
This PR contains all the code changes and #472 handles all of the publish warnings.
#472 fails, as parse_server_sdk: ^1.0.28 does currently not exist.

I am not quite sure if we decided to use parse_server_sdk_flutter as the flutter-package's name, or if this was a temporary thing.
Changing it should be quickly done.

This is still an option.

nstrelow and others added 4 commits October 9, 2020 20:52
* Add disclaimer to not use Masterkey on client side
Fix bug where whereMatchesKeyInQuery cant be used when using different object classes.
Not sure how this line got lost.
@phillwiggins
Copy link
Member

Okay cool.

@fischerscode The release process does not depend on this being merged in, however, we should do that straight way. Which package shall I release? Shall I just release the Flutter project at the moment or would you like me to publish both?

@fischerscode
Copy link
Contributor Author

@phillwiggins

Shall I just release the Flutter project at the moment

I didn't thought about that option, it sounds good, too. But we would have to replace this with something like this.

  parse_server_sdk:
    git:
      url: git://github.com/parse-community/Parse-SDK-Flutter.git
      ref: release/1.0.28
      path: packages/dart

But then flutter pub publish --dry-run for the flutter package results in this warning:

Package validation found the following potential issue:
* Don't depend on "parse_server_sdk" from the git source. Use the hosted source instead. For example:
  
  dependencies:
    parse_server_sdk: ^1.0.27
  
  Using the hosted source ensures that everyone can download your package's dependencies along with your package.

Package has 1 warning.
pub finished with exit code 65

So I think publishing both packages is the only option.

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

@fischerscode
Copy link
Contributor Author

I think you have to run the publish command inside of packages/dart as well as inside of packages/flutter. At least that's how I run flutter pub publish --dry-run.

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

@fischerscode
Copy link
Contributor Author

@phillwiggins
Great. I've changed the dependency in my app. It seems to work.
You have published from the current release 1.0.28 branch including the changes from #472, right?
If you don't mind, I would merge #472, then #460 and create a new dev branch (1.0.29(?)) afterwards.

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

* added licenses

I've just copied the LICENSE file.

* change dependencies at dart/pubspec.yaml

* change dependencies at flutter/pubspec.yaml
It's contained in the pub.spec archive, so I add it here.
@fischerscode fischerscode merged commit e35d28d into master Oct 11, 2020
@fischerscode
Copy link
Contributor Author

@phillwiggins
I think it's all done now.
Just two more things:

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

@fischerscode
Copy link
Contributor Author

@phillwiggins
I think, you are right. https://pub.dev/help/scoring#support-multiple-platforms
The web label for the dart package may be absent, as files like this do not have a default, that's independent from all platforms.
Should we add this to the next release or is updating a package possible?

@fischerscode
Copy link
Contributor Author

fischerscode commented Oct 11, 2020

as files like this do not have a default, that's independent from all platforms.

It should be done like so

@phillwiggins
Copy link
Member

phillwiggins commented Oct 11, 2020 via email

@fischerscode
Copy link
Contributor Author

fischerscode commented Oct 11, 2020

Your call. I don't mind releasing it again? Bump it to 1.0.28+1

All right, I will push a commit later.

@fischerscode
Copy link
Contributor Author

I will push a commit later

Unfortunately I ran out of time today. I am going to get back to this tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants