-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Release/1.0.28 #460
Conversation
- 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
Release/1.0.28
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
* split code into package directories * removed unused dependencies * Updated READMEs
…-Flutter into release/1.0.28
Fix LiveQuery reconnect
* 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
@phillwiggins |
* 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
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
@phillwiggins
This is still an option. |
* 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.
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? |
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
So I think publishing both packages is the only option. |
Oh okay. I'm not quite sure what the best way forward is for that. Would I
publish the package as normal or from the root? I'd imagine if it is from
root, it will never be split into 2 packages.
…On Sun, 11 Oct 2020, 08:47 Maximilian Fischer, ***@***.***> wrote:
@phillwiggins <https://github.com/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
<https://github.com/parse-community/Parse-SDK-Flutter/blob/7a4d4a4f51abe6ee69a1ffe829c32da987cd4412/packages/flutter/pubspec.yaml#L13>
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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXXI3HX4KOQOTAO4U7DSKFPH3ANCNFSM4SBTKCGQ>
.
|
I think you have to run the publish command inside of |
Okay cool. Will do that now.
…On Sun, 11 Oct 2020, 09:42 Maximilian Fischer, ***@***.***> wrote:
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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXWBFMLT4FIQTDMGQFTSKFVWDANCNFSM4SBTKCGQ>
.
|
Both have been published. I had to amend the Flutter dependency. It is
required to point at the dart parse server sdk on pub.dev to work.
I've not tested it yet, but let me know how it goes.
…On Sun, 11 Oct 2020 at 09:44, Phill Wiggins ***@***.***> wrote:
Okay cool. Will do that now.
On Sun, 11 Oct 2020, 09:42 Maximilian Fischer, ***@***.***>
wrote:
> 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.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#460 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB4CPXWBFMLT4FIQTDMGQFTSKFVWDANCNFSM4SBTKCGQ>
> .
>
--
Kind Regards
Phill Wiggins
[email protected]
|
@phillwiggins |
That is correct.
…On Sun, 11 Oct 2020 at 10:30, Maximilian Fischer ***@***.***> wrote:
@phillwiggins <https://github.com/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
<#472>, right?
If you don't mind, I would merge #472
<#472>, then #460
<#460> and
create a new dev branch (1.0.29(?)) afterwards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXX3QSAKHEUTSUOUYUDSKF3MBANCNFSM4SBTKCGQ>
.
--
Kind Regards
Phill Wiggins
[email protected]
|
* 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.
@phillwiggins
|
I think (not 100% certain) that these tags are supplied via the
pubspec.yaml. I think there's some types of flags that dictate which badges
are set on the pub.dev page.
I might need to look further into that.
…On Sun, 11 Oct 2020 at 11:20, Maximilian Fischer ***@***.***> wrote:
@phillwiggins <https://github.com/phillwiggins>
I think it's all done now.
Just two more things:
- https://pub.dev/packages/parse_server_sdk says, that the package is
only for dart-native. I think dart-web should work, too. And it says it's a
dart and flutter package. Even through this is technically correct,
wouldn't it be reasonable to remove the flutter label, as the flutter
package should be used for flutter projects?
- And I think, https://pub.dev/packages/parse_server_sdk_flutter
should now show the web compatibility label.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXUYW7ROZVYU2QUXAT3SKGBGZANCNFSM4SBTKCGQ>
.
--
Kind Regards
Phill Wiggins
[email protected]
|
@phillwiggins |
Your call. I don't mind releasing it again? Bump it to 1.0.28+1
…On Sun, 11 Oct 2020, 12:39 Maximilian Fischer, ***@***.***> wrote:
@phillwiggins <https://github.com/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
<https://github.com/parse-community/Parse-SDK-Flutter/blob/master/packages/dart/lib/src/network/http_client_adapter.dart>
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?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#460 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXQ4SEJT5PNNRZ2F4DLSKGKOHANCNFSM4SBTKCGQ>
.
|
All right, I will push a commit later. |
Unfortunately I ran out of time today. I am going to get back to this tomorrow. |
TODO before merging:
parse_server_sdk
dependency to pub.dev changed with 1.0.28/fix publish warnings #472TODO after merging:
parse_server_sdk_flutter
at pub.dev