Daniel Hochman

Results 36 issues of Daniel Hochman
trafficstars

**Description** Create docker-compose example (or maybe top-level docker-compose?) launching clutch with postgres. Complexity [S/M/L]: S

type: enhancement
area: ci

**Description** Okta and other auth providers provide profile information beyond email, such as first and last name. We could incorporate this information into the Clutch claims and use it to...

type: enhancement
area: frontend
area: backend

**Description** Add .yarnrc version lock to scaffolding similar to what we have in the core project, requiring a specific version of yarn. For more context see the discussion here: https://github.com/lyft/clutch/pull/461/files#r493711360...

type: enhancement

**Description** > It would be awesome if we had the text field component configurable to trim leading and trailing whitespace such that the user can see it and it'll be...

type: enhancement
area: frontend

**Description** Pop an additional confirmation modal or interstitial for risky actions. In the future, this may be server-controlled with risk scoring to determine whether or not to pop the modal....

type: enhancement
area: frontend

**Description** data-layout should somehow support polling, probably via its hooks. Maybe something like: ```jsx const myStatus = useDataLayout("status", { refreshInterval: "5s" }); ``` This will also be great when paired...

type: enhancement
area: frontend
status: needs-design

**Description** Custom gateways generated from scaffolding depend on the core Go/JS but there is no good way to keep these dependencies in sync. The Clutch core components published to npm...

type: enhancement
area: ci

**Description** If I fill in something for the free-form section and empty it out, the form does not recognize that it should use the structured search and instead enforces require...

type: bug
area: frontend

**Description** Resolver does not work properly with router history. **Expected Behavior** Clicking back after submitting the resolver would allow me to edit my selections and resubmit. **Actual Behavior** Clicking back...

type: bug
area: frontend

**Description** Report on coverage for both frontend and backend (separately?). Eventually we will want to enforce as well. My only real preference is that we can have it report using...

type: enhancement
area: ci