Skip to content

[web] implement PluginUtilities for flutter web #33615

Closed as not planned
Closed as not planned

Description

@jonahwilliams

...or don't, maybe it doesn't make sense.

Activity

  1. modified the milestones: June 2019, , on Jun 6, 2019
  2. amreniouinnovent commented on Dec 15, 2019

    @amreniouinnovent

    @jonahwilliams I think if you added a suggested PluginUtilities List then the developers could vote on it

  3. goderbauer commented on Mar 26, 2020

    @goderbauer
    Member

    Related: #33614

    @jonahwilliams @yjbanov Have you given it any thought if these APIs would be implementable on the web? They could help us with restoring anonymous routes. That problem is described in http://flutter.dev/go/restoring-anonymous-routes and PluginUtilities.getCallbackHandle / PluginUtilities.getCallbackFromHandle could be an alternative to Ephemerons to solve it.

    For reference, the sub-problem that these APIs are solving for us is the following:

    Given a static function we need to be able to obtain a serializable identifier for that function. And given that serializable identifier (in another instance of the app) we need to be able to re-obtain the original function object.

  4. jonahwilliams commented on Mar 26, 2020

    @jonahwilliams
    ContributorAuthor

    Anything involving isolates is not implementable on the web.

  5. goderbauer commented on Mar 26, 2020

    @goderbauer
    Member

    The API itself is independent of isolates as far as I can tell.

  6. jonahwilliams commented on Mar 26, 2020

    @jonahwilliams
    ContributorAuthor

    Depends on what you mean by implement - we could no-op it certainly, but we can't get handles to callbacks that can be shared across isolates.

  7. leafpetersen commented on Mar 26, 2020

    @leafpetersen
    Contributor

    Under the assumptions that:

    • the callback is a static function (not a closure)
    • there isn't version skew between the serializing code and the deserializing code

    I don't see any reason why it should be impossible to do what @goderbauer is looking for in JS. @sigmundch @rakudrama could possibly provide more accurate commentary.

    Just because it's possible in principle though doesn't mean that it would just fall out of the current compilation strategy . But I actually think it might not be far off - you could use a class ID plus a static method name maybe?

  8. sigmundch commented on May 9, 2020

    @sigmundch
    Contributor

    Sorry for the very slow response here.

    Is the expectation that the serialized id is usable within a single version of the app or across multiple versions? I don't see a reason why the former can't be supported, but the latter could be problematic.

    Many teams consider the names of their methods internal and/or sensitive, so we wouldn't want to use the original class/method name as part of the serialized form. When we minify an application, the minified name would work, but that is not stable across multiple compilations of the program.

  9. 23 remaining items

  10. added
    P3Issues that are less important to the Flutter project
    f: routesNavigator, Router, and related APIs.
    and removed
    P2Important issues not at the top of the work list
    on Sep 15, 2020
  11. added
    team: skip-testAn issue used to track tests that are skipped.
    c: tech-debtTechnical debt, code quality, testing, etc.
    on Jul 29, 2021
  12. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    a: pluginsSupport for writing, building, and running plugin packages
    and removed on Mar 11, 2023
  13. github-actions commented on Jul 14, 2025

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  14. locked as resolved and limited conversation to collaborators on Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: pluginsSupport for writing, building, and running plugin packagesc: new featureNothing broken; request for a new capabilityc: tech-debtTechnical debt, code quality, testing, etc.dependency: dartDart team may need to help usf: routesNavigator, Router, and related APIs.frameworkflutter/packages/flutter repository. See also f: labels.platform-webWeb applications specificallyteam-webOwned by Web platform teamteam: skip-testAn issue used to track tests that are skipped.triaged-webTriaged by Web platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions