From ed9278c5970e302caa24d1eceb23c1be78aea30c Mon Sep 17 00:00:00 2001 From: Jonas Finnemann Jensen Date: Mon, 31 Jul 2023 16:15:59 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Christopher Fujino --- pkgs/extension_discovery/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pkgs/extension_discovery/README.md b/pkgs/extension_discovery/README.md index ec87bd56a..d84ab3795 100644 --- a/pkgs/extension_discovery/README.md +++ b/pkgs/extension_discovery/README.md @@ -1,19 +1,19 @@ # Package Extension Discovery -A convention to allow other packages to provide extension for your package -(or tool). Including logic for finding extensions that honors this convention. +A convention to allow other packages to provide extensions for your package +(or tool). Including logic for finding extensions that honor this convention. The convention implemented in this package is that if `foo` provides an extension for ``. Then `foo` must contain a config file `extension//config.json`. -This file indicates that `foo` provides and extension for ``. +This file indicates that `foo` provides an extension for ``. If `` accepts extensions from other packages it must: * Find extensions using `findExtensions('')` from this package. * Document how extensions are implemented: * What should the contents of the `extension//config.json` file be? - * Should packages providing extension have a dependency constraint on ``? - * What libraries/assets should packages that provide extension include? + * Should packages providing extensions have a dependency constraint on ``? + * What libraries/assets should packages that provide extensions include? * Should packages providing extensions specify a [topic in `pubspec.yaml`][1] for easy discovery on pub.dev.