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-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,8 @@ Provided is support for decoding a NestedText file or string to Ruby data struct
27
27
28
28
This library is inspired by Ruby's stdlib modules `JSON` and `YAML` as well as the Python [reference implementation](https://github.com/KenKundert/nestedtext) of NestedText. Parsing is done with a LL(1) recursive descent parser and dumping with a recursive DFS traversal of the object references.
29
29
30
-
To make this library practically useful, you should pair it with a [schema validator](#schema).
30
+
> [!TIP]
31
+
> To make this library practically useful, you should pair it with a [schema validator](#schema).
31
32
32
33
# What is NestedText?
33
34
Citing from the official [introduction](https://nestedtext.org/en/latest/index.html) page:
See [encode_custom_classes_test.rb](test/nestedtext/encode_custom_classes_test.rb) for more real working examples.
253
+
> [!TIP]
254
+
> See [encode_custom_classes_test.rb](test/nestedtext/encode_custom_classes_test.rb) for more real working examples.
253
255
254
256
# Schema
255
257
The point of NestedText is to not get in to business of supporting ambiguous types. That's why all values are simple strings. Having only simple strings is not useful in practice though. This is why NestedText is intended to be paired with a [Schema Validator](https://nestedtext.org/en/latest/schemas.html)!
0 commit comments