comparison tests/test-topic-stack.t @ 2805:a789b9d5b60c stable

topic: make command names valid as expected, even if ui.strict=true Before this patch, "hg topics" and "hg stack" cause unintentional "unknown command" failure, if ui.strict=true. In such case, "topics [TOPIC]" and "stack [TOPIC]" are required as a canonical name, because synopsis-like string is used as command name pattern of @command annotation for them. This patch also specifies additional "synopsis" for @command annotation, for intentional output in online help of these commands.
author FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
date Sun, 23 Jul 2017 13:30:28 +0900
parents bd3824d1b795
children f25c79365f5d 8874e65343a4
comparison
equal deleted inserted replaced
2804:bae174e0e0ac 2805:a789b9d5b60c
185 ], 185 ],
186 "topic.stack.state.symbol": "^" 186 "topic.stack.state.symbol": "^"
187 } 187 }
188 ] 188 ]
189 189
190 check that topics and stack are available even if ui.strict=true
191
192 $ hg topics
193 * foo
194 $ hg stack
195 ### topic: foo
196 ### branch: default
197 t4@ c_f (current)
198 t3: c_e
199 t2: c_d
200 t1: c_c
201 t0^ c_b (base)
202 $ hg topics --config ui.strict=true
203 * foo
204 $ hg stack --config ui.strict=true
205 ### topic: foo
206 ### branch: default
207 t4@ c_f (current)
208 t3: c_e
209 t2: c_d
210 t1: c_c
211 t0^ c_b (base)
212
190 error case, nothing to list 213 error case, nothing to list
191 214
192 $ hg topic --clear 215 $ hg topic --clear
193 $ hg stack 216 $ hg stack
194 ### branch: 217 ### branch: