AssetImage docs improvements

[Hixie]

AssetImage docs has a "Fetching assets" section but that section doesn't actually tell you how to fetch an asset, it just tells you how to specify a name when you're not in a package.

We should have a section that talks about how to actually fetch an asset (i.e. how to use the class).

[Hixie]

It can probably just point to ImageProvider, which has a "Using an ImageProvider" section.

[Swayam221]

I would like to work on this issue. Can I please be assigned to this?

[Hixie]

@Swayam221 No need to be assigned, just submit a PR! Thanks, looking forward to it!

[Swayam221]

@Hixie

It can probably just point to ImageProvider, which has a "Using an ImageProvider" section.

So, should I just include a link to the docs for ImageProvider there?

[Hixie]

Well you'd want to make the text flow nicely, and so on. I haven't looked at exactly what would need to happen, if I had, I would just make the change directly. :-) Figuring out what the change should be is 90% of the work.

[Swayam221]

@Hixie I think if we point it to this link https://flutter.dev/docs/development/ui/assets-and-images#loading-images-1 , it will be well understandable.
Can you please guide me so that I can add an hyperlink in the src/painting/image_resolution.dart file for this?

[Hixie]

I recommend starting with the contributing docs:
https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md

[Swayam221]

@Hixie please review #78173

[mateusfccp]

I think we could use also this issue to fix some instances of AssetImage in the ExactAssetImage documentation.

See lines 1010 and 1020 below:

[Swayam221]

@mateusfccp what do you exactly mean by 'fix some instances of AssetImage' ?

[Swayam221]

@Hixie review requested on linked PR at #78173

[mateusfccp]

@mateusfccp what do you exactly mean by 'fix some instances of AssetImage' ?

As it shows in the image I provided, there are some samples on the ExactAssetImage documentation that uses AssetImage instead.

[Swayam221]

@mateusfccp Oh yes, I see. Should I change this as well, @Hixie ?

[Hixie]

Let's keep each individual issue separate for now, it becomes more complicated when things are mixed. Separate bug, separate PR, etc.

[mateusfccp]

@Hixie I see, I am going to open a separate PR, then. Is it a must to create an issue too?

[Hixie]

It's ideal to have one issue per PR and one PR per issue at least until you are an experienced contributor. :-)

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