Skip to content

Commit b80f30a

Browse files
committed
Updated roadmap.
1 parent 25defde commit b80f30a

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

README.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -47,17 +47,12 @@ The following is a list of features that are planned for the future:
4747
- [ ] Add support for YAML.
4848
- [ ] Add support for TOML.
4949

50-
Each format Pasper provides support for will be contained in its own assembly to allow consumers to only include the formats they need. The naming convention for these assemblies will be `Pasper.{Format}.{Provider}`, for example:
50+
Each format Pasper provides support for will be contained in its own assembly to allow consumers to only include the formats they need. The naming convention for these assemblies will be `Pasper.{Format}`, for example:
5151

52-
- `Pasper.Json.Newtonsoft`
53-
- `Pasper.Yaml.YamlDotNet`
52+
- `Pasper.Json`
53+
- `Pasper.Yaml`
5454

55-
The provider name for `System` namespaces is currently up for debate:
56-
57-
- `Pasper.Json.System` or `Pasper.Json.Microsoft`
58-
- `Pasper.Xml.System` or `Pasper.Xml.Microsoft`
59-
60-
This will allow consumers to easily identify not only the format they're after, but the provider they want to use as well.
55+
This will allow consumers to easily identify the format they're after, and only include the assemblies they need.
6156

6257
### 🆘 What problem does Pasper aim to solve
6358

0 commit comments

Comments
 (0)