Skip to content

Using a resource not listed in flutter.yaml should show a red X #125

Closed

Description

@FlutterIssues

Issue by eseidelGoogle
Tuesday Aug 11, 2015 at 21:01 GMT
Originally opened as https://github.com/flutter/engine/issues/565


We need to make it a visual as well as console error to use a resource not listed in that file or skyx packing won't work correctly.

Probably a change to ResourceBundle? @abarth

Activity

  1. abarth commented on Nov 10, 2015

    @abarth
    Contributor

    We have a console error but not a visual error.

  2. changed the title [-]It should be an error to use a resource not listed in sky.yaml[/-] [+]It should be an error to use a resource not listed in flutter.yaml[/+] on Nov 10, 2015
  3. added this to the milestone on Dec 12, 2015
  4. Hixie commented on Dec 12, 2015

    @Hixie
    Contributor

    We now just don't render the image. Do you want more? Some sort of uglified red square with a cross or something?

  5. changed the title [-]It should be an error to use a resource not listed in flutter.yaml[/-] [+]Using a resource not listed in flutter.yaml should show a red X[/+] on Jan 23, 2017
  6. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    on Jan 23, 2017
  7. modified the milestones: , on May 30, 2017
  8. zoechi commented on Nov 29, 2018

    @zoechi
    Contributor

    #18898 might be a neat solution for that.
    Dart code generated from yaml would cause analyzer errors for using non-existing const references.

  9. zoechi commented on Jan 21, 2019

    @zoechi
    Contributor

    Related to #11477

  10. jonahwilliams commented on Jun 14, 2019

    @jonahwilliams
    Contributor

    We might want to revist implementing something similar for the web. In the case where the user has a FileImage, we should show something like a red box instead of crashing. We should make that image behavior as general as reasonably possible too

  11. 3 remaining items

  12. removed this from the milestone on Jun 1, 2020
  13. self-assigned this
    on Jan 29, 2021
  14. Hixie commented on Jan 29, 2021

    @Hixie
    Contributor

    Fixed by #74972.

  15. github-actions commented on Aug 6, 2021

    @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.

  16. locked as resolved and limited conversation to collaborators on Aug 6, 2021
  17. added
    P3Issues that are less important to the Flutter project
    and removed on Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projecta: assetsPackaging, accessing, or using assetsa: error messageError messages from the Flutter frameworka: imagesLoading, displaying, rendering imagesc: new featureNothing broken; request for a new capabilityframeworkflutter/packages/flutter repository. See also f: labels.waiting for PR to land (fixed)A fix is in flight

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions