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

update readme with more information #78

Closed
devoncarew opened this issue Jun 5, 2023 · 3 comments · Fixed by #119
Closed

update readme with more information #78

devoncarew opened this issue Jun 5, 2023 · 3 comments · Fixed by #119

Comments

@devoncarew
Copy link
Member

Now that this package is published, we should update the readme with a bit more information:

  • what's the package? what's it used for?
  • a (brief) code example?
  • references to more comprehensive documentation

cc @polina-c

@polina-c
Copy link
Contributor

polina-c commented Jun 6, 2023

The package is still under construction and is constantly changing.
It is published for internal use only for now.
As soon as the package stabilizes, I will update readme.

This task is tracked under flutter/devtools#3951

So, closing this issue as duplicate

@polina-c polina-c closed this as completed Jun 6, 2023
@devoncarew
Copy link
Member Author

It is published for internal use only for now.

Gotcha, understood. FYI, I updated the status at https://pub.dev/packages/leak_tracker/admin to 'unlisted'; that means the package will not show on pub.dev search results. You can toggle that back at any time once this package is meant to be more visible.

@devoncarew devoncarew reopened this Aug 4, 2023
@devoncarew
Copy link
Member Author

We should update the readme with the info in the first comment (for both packages leak_tracker and leak_tracker_testing). They're both published, in tools.dart.dev, and on non pre-release versions; we really need more than 'coming soon'.

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 a pull request may close this issue.

2 participants