-
-
Notifications
You must be signed in to change notification settings - Fork 206
fix some issues #216
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
fix some issues #216
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please can you check my comments before commit? There's a few things that look confusing.
@@ -64,7 +64,7 @@ class _MyAppState extends State<MyApp> { | |||
Future<void> initData() async { | |||
// Initialize repository | |||
await initRepository(); | |||
final CoreStore coreStore = await initCoreStore(); | |||
// final CoreStore coreStore = await initCoreStore(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why has this been removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bwcause it is not used yet. so I comment it out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a big and will need to be investigated further.
@@ -100,6 +102,7 @@ abstract class ParseBase { | |||
map.remove(keyVarUpdatedAt); | |||
map.remove(keyVarClassName); | |||
//map.remove(keyVarAcl); | |||
map.remove(keyVarObjectId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we sure this is correct for all calls? Seems strange that it's there in the first place. Have you ran tests that everything else works with this removed? Rather than just installation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do all the test in example. yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this works when saving?
I'm not sure saving an object would work anymore. It will create a new object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@phillwiggins
I'm seeing that they removed the ACL from ParseObject, the code was commented out. When was it done? I've added this functionality to lib and am using this in version 21 on a large project and have not had problem.
Apologies, I've just noticed as well, we are ok branch release/1.0.23 now. Please can you make a PR there instead. |
ok, I will check it tomorrow. it's time to sleep here. |
Ah apologies! Thanks for your effort by the way.
…On Wed, Jul 10, 2019, 17:39 Zenz ***@***.***> wrote:
ok, I will check it tomorrow. it's time to sleep here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#216>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4CPXVSGT6D7AZBYIPZUCDP6YGDHANCNFSM4H7QNSTA>
.
|
@phillwiggins |
@RodrigoSMarques
And here's the samples to test this SDK v 1.0.23 with livequery. |
fix liveQuery.subscribe issue.
fix installation issue.
It's now working with my livequery sample.