demos: use sentence case for every field label

Open Beginner friendly
  • Is something wrong?
#188 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
angular, tailwindcss, typescript
Domain
frontend

Research direction

Start in libs/demo-shared/src/lib/demo-resources.ts and check how the three resources define field names and labels. Run the demo-material and demo-tailwind demos to inspect list, show, create, and edit pages, then update tests that expect the old labels. Done when all headers and field labels use the requested sentence case and both Nx test commands pass.

Written by the indexing model from the issue text.

Description

good first issue layer: demo

What is wrong

Column and field labels in the demos mix lower case and capitals: "id", "name", "email", "price", "total" next to "User" and "Created at".

How to see it

Open https://pidrang.dev/demo-material/orders: the headers read "id", "User", "total", "Created at".

Where to look

libs/demo-shared/src/lib/demo-resources.ts: only user_id and created_at have a label; the other fields show their name.

Steps

  1. Add a label in sentence case to every field that has none: "ID", "Name", "Email", "Price", "Total".
  2. Run both demos and check the list, show, create and edit pages.
  3. Run pnpm exec nx test demo-material and pnpm exec nx test demo-tailwind, and update the tests that look for the old text.

Done when

  • Every header and field label of the three resources is in sentence case, in both demos.
  • The tests pass.
Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
9h 17m
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pidrang/pidrang

All issues in pidrang/pidrang

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.