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
Aggregate parsers have been introduced as a better version of the compound parsers. You may either implement the aggregate parser interface, or construct an aggregate parser using a builder. The aggregate parsers support suggestion provider overrides for the inner components, which was not possible with the compound parsers.
53
53
54
-
The compound parsers implement the aggregate parser interface, and thus gets access to the improvements. The existing command builder methods for building argument pairs and triplets will remain.
Commands now have descriptions that live outside the command meta. This is different from the description of the root literal of a command. The new `CommandDescription` class replaces the old `DESCRIPTION` and `LONG_DESCRIPTION` meta values.
58
56
@@ -106,10 +104,27 @@ You may now register `ParserDescriptor` instances.
106
104
**Move confirmation system to external repository ([#620](https://github.com/Incendo/cloud/pull/620))**
107
105
The confirmation system now lives in [cloud-processors](https://github.com/Incendo/cloud-processors).
108
106
109
-
**Add Either ([647](https://github.com/Incendo/cloud/pull/647))**
107
+
**Add Either ([#647](https://github.com/Incendo/cloud/pull/647))**
110
108
`Either<A, B>` can be parsed by `ArgumentParser.firstOf(ParserDescriptor, ParserDescriptor)` which allows
111
109
for multiple variable components on the same level.
0 commit comments