Improve template ref handling
refactor(template-ref): improve template ref handling
Improve template ref handlingrefactorimprove template ref handling
Committed by yyx990803
commit message
refactor(template-ref): improve template ref handling
close #836, close #839Editor assessment
The header's vagueness is the problem: 'improve template ref handling' could mean anything from a performance tweak to an API change, and refactor is asserted without evidence in the message. The body's 'close #836, close #839' suggests these were outstanding issues — possibly bug reports, which would argue for fix instead — but no reader can tell without opening them. Combining two close tokens on one comma-separated line works for GitHub, though the strict token format favors one footer per line. refactor(template-ref) and the imperative-ish subject are fine; the missing 'what actually changed' is not.