Gather and resolve namespace beefs (and maybe figure out process of continuous improvement) 🥩

[patcon]

Re-ticketed from: https://easyretro.io/publicboard/ADTFk5S1DIUfT6BLwZieAEdeUP82/20bdce11-7c34-4c41-9a8b-90f05c3d5795

[vd1992]

classification vs expectedClassification vs genericClassification

[mnigh]

seems like this has been resolved as there is no longer expectedClassification or genericClassification:

• [Debt] Removes expectedClassifications, expectedSalary, expectedGenericJobTitle #7578
• [Debt] Remove expectedSalary and expectedClassification fields from schema #7997

[patcon]

• SingleSearchRequest.tsx
  • Page suffix?
  • View vs List prefix?

cc: @yonikid15

[mnigh]

@yonikid15 is this still an issue and if so, can you describe? SingleSearchRequest.tsx doesn't seem to exist anymore.

[patcon]

We should have a word for when a component/page takes multiple vs single. And we shouldn't confuse naming by having "single" elsewhere in the name :)

E.g., in API design, usually "list" is used as verb and noun for the plural endpoints, and it's absence and use of singular (or sometimes "view" keyword) is used to say it accepts one. Like FooView (single) vs FooList (multiple) to show whether one or multiple of the main objects are passed in, aka an object or an array or objects is the type of thing its passed.

Maybe this isn't as clean for components (compared to APIs that mostly deal with one entity per named endpoint), but still room for improvement perhaps :)

[patcon]

anon comment in 2022-12-14 retro: https://easyretro.io/publicboard/Bb8eeNIEzucUDrcOv0T1LaCp71m1/6b44c3d4-02f6-4309-a2e9-7378f16ea304

overly descriptive enums and more precise language all around.

same goes for form labels

Maybe related, re: form labels. #3314