Skip to content

🎨 Palette: unique customer IDs for clearer CLI demos#25

Merged
ruhdevops merged 2 commits intomainfrom
palette-unique-customer-ids-7424792465259260553
Apr 11, 2026
Merged

🎨 Palette: unique customer IDs for clearer CLI demos#25
ruhdevops merged 2 commits intomainfrom
palette-unique-customer-ids-7424792465259260553

Conversation

@ruhdevops
Copy link
Copy Markdown
Owner

🎨 Palette: Unique Customer IDs in Demo Scripts

💡 What

Replaced random.choices with random.sample for mock data generation in 01_getting_started.py and 02_logging.py.

🎯 Why

In small-scale CLI demos, duplicate IDs (e.g., seeing "customer-51" twice in a list of five) can look like a bug to developers trying out the scaffold. Ensuring uniqueness makes the output clearer and more realistic.

♿ Accessibility & UX

  • Improves visual clarity by preventing duplicate rows in summary tables.
  • Follows the principle of "Information Density" by ensuring every row represents a distinct entity.
  • Updated the UX journal at .Jules/palette.md.

PR created automatically by Jules for task 7424792465259260553 started by @ruh-al-tarikh

This change replaces `random.choices` with `random.sample` in the
`get_customer_ids` tasks within `01_getting_started.py` and
`02_logging.py`. Using `random.choices` could occasionally lead to
duplicate customer IDs in the summary tables, which can be confusing
for users following the tutorial. `random.sample` ensures that the
five generated IDs are unique, providing a more professional and
realistic demo experience.

Added a corresponding entry to `.Jules/palette.md` to document this
UX improvement.

Co-authored-by: ruh-al-tarikh <203426218+ruh-al-tarikh@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@ruhdevops ruhdevops marked this pull request as ready for review April 7, 2026 05:14
@ruhdevops ruhdevops self-assigned this Apr 11, 2026
@ruhdevops ruhdevops merged commit ba6a905 into main Apr 11, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant