You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-9Lines changed: 4 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -47,17 +47,12 @@ The following is a list of features that are planned for the future:
47
47
-[ ] Add support for YAML.
48
48
-[ ] Add support for TOML.
49
49
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:
51
51
52
-
-`Pasper.Json.Newtonsoft`
53
-
-`Pasper.Yaml.YamlDotNet`
52
+
-`Pasper.Json`
53
+
-`Pasper.Yaml`
54
54
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.
0 commit comments