Page MenuHomePhabricator

Make `bin/lipsum generate` hanldle generator keys and arguments more clearly
ClosedPublic

Authored by epriestley on Feb 27 2017, 12:20 PM.
Tags
None
Referenced Files
F19914379: D17420.id41895.diff
Fri, Apr 3, 10:41 AM
F19911424: D17420.id41895.diff
Thu, Apr 2, 11:48 AM
F19909778: D17420.id41895.diff
Thu, Apr 2, 2:27 AM
F19518319: D17420.diff
Jan 15 2026, 7:37 PM
F19516312: D17420.id.diff
Jan 14 2026, 10:38 PM
F19512736: D17420.diff
Jan 13 2026, 1:51 AM
F19153776: D17420.id41889.diff
Dec 11 2025, 12:07 PM
F19060576: D17420.diff
Nov 29 2025, 9:43 AM
Subscribers
None

Details

Summary

Ref T12319. Currently, bin/lipsum uses substring matches against human-readable text to chose which objects to generate.

Instead:

  • Use separate selector keys which are guaranteed to be unique.
  • When a match is exact, select only that generator.
  • When a match is ambiguous, fail and warn the user.
Test Plan

Generated several types of objects, tried to generate ambiguous objects like "e".

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable