If you only use the AssetPicker.pickAssets
and AssetEntityImageProvider
,
didn't use AssetPickerViewer
, AssetPickerProvider
, or other components separately,
you can stop reading.
AssetPicker
and AssetPickerViewer
are only a builder since 5.x, all widgets construct were moved
to AssetPickerBuilderDelegate
and AssetPickerViewerBuilderDelegate
, and these delegates are both
abstract.
By splitting delegates, now you can build your own picker with custom types, style, and widgets.
For how to implement a custom picker, see the example's custom page for more implementation details.
-
If you have ever use
AssetPickerViewer.pushToViewer
, the propertiesassets
has changed topreviewAssets
. -
If you have extends an
AssetPickerProvider
orAssetPickerViewerProvider
, it now requires you to pass generic typeA
andP
, and handle the entities on your own.
API documentation:
AssetPickerBuilderDelegate
: https://pub.dev/documentation/wechat_assets_picker/latest/wechat_assets_picker/AssetPickerBuilderDelegate-class.htmlAssetPickerViewerBuilderDelegate
: https://pub.dev/documentation/wechat_assets_picker/latest/wechat_assets_picker/AssetPickerViewerBuilderDelegate-class.htmlAssetPickerProvider
: https://pub.dev/documentation/wechat_assets_picker/latest/wechat_assets_picker/AssetPickerProvider-class.htmlAssetPickerViewerProvider
: https://pub.dev/documentation/wechat_assets_picker/latest/wechat_assets_picker/AssetPickerViewerProvider-class.html