chore: improve the package scores #513
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
the example increase the package score
the screenshot shows on the side bar and it increase the package usage since it make the package appears in Has screenshots
|
@hesham04Dev is attempting to deploy a commit to the FlutterTools Team on Vercel. A member of the Team first needs to authorize it. |
tilucasoli
changed the title
|
LGTM |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
adding screenshots (only logo)
adding an example increase the package score
Changes
create a new directory to add screenshots
create a very simple example in mix package
Review Checklist
Additional Information (optional)
To ensure changes take effect on pub.dev, you’ll need to publish a new version of your package. A simple patch update will work for minor adjustments; just increment the last digit of your version number (e.g., from 1.0.0 to 1.0.1). Don’t forget to update the changelog to document what’s new in this patch, as it helps users understand the purpose of the update.