Pub.dev documentation at_location_flutter

[ksanty]

Lead: @sarika01
Review ticket #342

Pub.dev content and (source)s - CHECKLIST OF TO DO's BELOW

All the content shown on pub.dev and where it comes from.
Example: Shelf (will point to one of our own once completed)

• Package name, version <pubspec.yaml>

• Published date (generated)

• Platform support (generated based on project structure)

• Tabbed navigation

  • Readme (note: initial content comes from readme.md)
  • Changelog example: firebase_auth
  • Example (github repo)
  • Installing (generated)
  • Versions (generated) <pubspec.yaml>
  • Scores (generated)
  • **Admin (generated)
  • **Activity log (generated)

• Right column

  • Scores (generated)
  • Publisher (generated)
  • Metadata <pubspec.yaml description>
  • Homepage <pubspec.yaml>
  • Repository (generated)
  • View/report issues (generated)
  • Documentation (generated)
    • Documentation url <pubspec.yaml>
    • API reference
  • License (github repo)
  • Dependencies (generated)
  • More (generated)

All items to be completed:

• Package should be implemented with rSDK
• Include an example (sample) app based on at_app skeleton
• Add example.md to explain how to run the sample app
• Ensure the readme.md follows the best practice template (WIP)
• Make sure and add in terms that will help get this package to the top of the search results
• Update changelog.md with clear description of the update
• Bump the version as appropriate in pubspec.yaml for the package
• Bump the version as appropriate in pubspec.yaml for the example
• Check that the description is accurate in pubspec.yaml for the package
• As appropriate, add a documentation link to atsign.dev for the package

[nitesh2599]

Published at_location_flutter 3.1.0

[sarika01]

Need to update repository link and add documentation link.

[sarika01]

Updated in at_location_flutter: ^3.1.1

[sarika01]

Published at_location_flutter: ^3.1.2