Please add migration guide docs

[husainazkas]

I have to handle existing project of flutter app that previously use this package at 2.0.3+3 version but now it must be migrated to the latest one.

Currently, I am facing some problems to do so. Many changes were made without docs, like borderRadius, margin, behavior, boxShadows, horizontalDismissDirection on Flash Widget, and so many others. Please add the docs ASAP, thank you.

[sososdk]

3.x changes are big, it is recommended to check the example.

[ycy1164656]

I have to handle existing project of flutter app that previously use this package at 2.0.3+3 version but now it must be migrated to the latest one.

Currently, I am facing some problems to do so. Many changes were made without docs, like borderRadius, margin, behavior, boxShadows, horizontalDismissDirection on Flash Widget, and so many others. Please add the docs ASAP, thank you.

Me also shocked by the incompatibility with the old version....wtf....

[vahidreza]

technically it was the worst i've ever encountered in a plugin update so far, its absolutely not backward compatible and with no proper documentation. please provide a way to address those issues.

[amanokerim]

@sososdk Please add migration guide like this:
https://github.com/singerdmx/flutter-quill/blob/master/doc/migration.md#from-700-to-800

[dev-thinks]

looks like completely rewritten from version 3.0+

Not able to upgrade from 2+ version. bump.

[princ3od]

Hi guys, I'm in the same situation I need to upgrade the Flutter version from 3.3.6 -> to 3.24.3 and also have a lot of trouble updating flash to a newer version due to many breaking changes without proper migration docs.
To address the issue, I temporarily try to migrate flash package v2.0.5+1 to work on the current latest Flutter version 3.24.3. You can check it here: https://github.com/princ3od/flash/tree/v2.0.5%2B1

Simply update this one in the pubspec.yml file:

  flash:
    git:
      url: https://github.com/princ3od/flash.git
      ref: 6197268cefa3a1abcc27913b9f9c3f8adf3d63ca # can be commit hash or branch name

I appreciate the author's effort in publishing this package. However, upgrading this package to v3 from v2 without migration docs would take weeks not months in my project. That means, in the meantime, I sill need to find a solution to overcome the root issue completely.