-
Notifications
You must be signed in to change notification settings - Fork 125
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
Added getSourceIds to the controller #197
Conversation
the requested changes are done like you asked @m0nac0 |
Sorry for noticing only now: could you add a button somewhere in the example app using this new function? That way we could manually test it (now and in the future) |
Yes, I was hesitant to do this when adding the feature so i'll do it later today Edit: tomorrow |
I added a page with get layer ids and get source ids |
Great thanks! I enabled auto-merge, if you could again update with the latest changes from main it should merge automatically. (Btw, I was able to confirm it works on iOS) |
Added getSourceIds to the controller with the android (tested) and ios (no ability to test here sorry). Not implemented on the web as getLayerIds in not implemented too I made the controller method returning a list of strings (`Future<List<String>>`) to have an explicit `String` list unlike `getLayerIds` who have a `Future<List<dynamic>>`
Added getSourceIds to the controller with the android (tested) and ios (no ability to test here sorry). Not implemented on the web as getLayerIds in not implemented too I made the controller method returning a list of strings (`Future<List<String>>`) to have an explicit `String` list unlike `getLayerIds` who have a `Future<List<dynamic>>`
Added getSourceIds to the controller with the android (tested) and ios (no ability to test here sorry). Not implemented on the web as getLayerIds in not implemented too
I made the controller method returning a list of strings (
Future<List<String>>
) to have an explicitString
list unlikegetLayerIds
who have aFuture<List<dynamic>>