Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: updating README to the new flame bloc version #1737

Merged
merged 5 commits into from
Jun 28, 2022

Conversation

erickzanardo
Copy link
Member

@erickzanardo erickzanardo commented Jun 16, 2022

Description

Updates the README to match the new API.

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • I have read the Contributor Guide and followed the process outlined for submitting PRs.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples.

Breaking Change

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Related Issues

Fixes #1695

@erickzanardo
Copy link
Member Author

cc @felangel

@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2021 Blue Fire
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -0,0 +1,55 @@
# Flame Bloc 🔥🧱
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps add a comment here about when this deprecated readme can be removed. This way we make sure the file won't linger forever.

[this](./DEPRECATED_README.md).

For a migration guide from the previous API to the current one,
[check this article](https://verygood.ventures/blog/flame-bloc-new-api).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

updateGear(state);
}
}
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might want to call out one limitation of the mixin is that a component cannot listen to multiple blocs

Copy link
Member

@spydon spydon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, once the requested changes from Felix are applied!
And I don't think that we should keep the deprecated readme file, potentially link to the old tagged version instead if you want the user to find it (but I don't think that is necessary either).


## ⚠️ IMPORTANT ⚠️ ##
This README only covers the new (>= 1.4.0) API of flame bloc, for the previous deprecated API check
[this](./DEPRECATED_README.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need this, if they want to read an old version of the readme they can look at the tag for an old version.

@erickzanardo erickzanardo enabled auto-merge (squash) June 28, 2022 00:28
@erickzanardo erickzanardo merged commit 6a2356a into main Jun 28, 2022
@erickzanardo erickzanardo deleted the erick.flame_bloc_updated_readme branch June 28, 2022 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[flame_bloc] Flame bloc README don't mention the new API.
5 participants