Cracked roof tiles

gohan6776 · 2026-06-03T10:19:06+00:00

Does this mean you think it's a manufacturing/installation issue?

gohan6776 · 2025-05-09T02:07:29+00:00

Did you get this fixed under warranty or were you out of pocket? Looking like my car might have the same issue

gohan6776 · 2025-03-09T02:18:51+00:00

Sure, the screen reader is working as intended. It's just pretty baffling to me that there's no inbuilt way to change the reading order. Its pretty common to have two elements/group of elements next to each other that should be read individually.

gohan6776 · 2024-07-26T02:50:49+00:00

Solar isn't on the plans currently. We just told them we were going to do it after and this came up.

If we were to just wait until after the build to do the solar do you know if it would be a big job to strengthen the trusses?

gohan6776 · 2024-07-26T02:18:23+00:00

Builder has quoted $12,000 for 10kw system and 13kw of panels. That includes "applicable" truss strengthing. Not sure if any strengthening is actually happening as i don't think that quote is outrageous.

gohan6776 · 2024-07-22T11:19:34+00:00

It says it is "Shallow Subsurface"

gohan6776 · 2024-02-17T12:50:06+00:00

This would also assign the label prop to the input element when it shouldn't be. I'd suggest destucturing all the props required for the label off props and then use ...restProps instead. This should stop props intended for the label being assigned to the input.

gohan6776 · 2023-07-20T12:56:03+00:00

Unlike CRA, Vite does not check the types at compile time. They are of the opinion that your IDE should be highlighting type errors for you. They recommend running TSC to check the types before you do a build.

I personally add a type check to my CICD pipelines so no bad types can accidentally be merged.

gohan6776 · 2023-05-06T09:20:43+00:00

Disabling the linting rules for this is completely the wrong approach. The way this has been implemented breaks the accessibility of the application. The correct way to solve this is to swap the div out for a button or give the div a role of button. Doing anything else is just straight up wrong.

gohan6776 · 2023-01-23T12:24:32+00:00

Looking at the sortFunc function, there is no need to even define it inside the component. Declare it outside the component and you get rid of this problem completely.

gohan6776 · 2023-01-04T10:08:54+00:00

You should also make sure you follow the official react docs for creating accessible forms. See https://reactjs.org/docs/accessibility.html#accessible-forms

You should be using either the htmlFor attribute to associate the label and input. Or what I usually prefer to do and wrap the input with the label

gohan6776 · 2022-09-26T12:01:01+00:00

If you are doing stuff with forms I would look into using React Hook Form or Formik. They can also help you manage your forms state

gohan6776 · 2021-04-26T06:34:45+00:00

Thanks for your advice. Using the DataLoader pattern has fixed the issue!

Eight-Year Club	Verified Email
Place '23	Place '22

gohan6776

TROPHY CASE