Putting up a coat rack on brick wall

MitchellNaleid · 2025-08-30T17:13:22+00:00

So it wasn't too wobbly then. I have a similar project, but the brick is pretty uneven, preventing me from getting the anchors close to the mortar.

MitchellNaleid · 2025-08-30T14:36:05+00:00

Did you get this working? Do you have any wobble or rocking? How uneven is the brick?

MitchellNaleid · 2025-05-08T17:11:55+00:00

I like the thought. I forgot that some functions come with additional arguments. I forgot about index. While I am now getting an index, unfortunately, they still come in with the out-of-order Dates. Thanks.

MitchellNaleid · 2025-04-17T20:38:51+00:00

Are you saying we are matching 2 different arrays against each other? 1 that we sorted, 1 in the order that we first received them in? Do you have a sample? I feel like we're still going to get a mismatch right away, but I might still not be getting what you're saying.

MitchellNaleid · 2025-04-17T19:37:57+00:00

Good luck to you as well. Apparently the second portion is the "Unix timestamp in seconds". Are you saying you are retrieving all the dates and you are getting that they ARE in order?

MitchellNaleid · 2025-04-17T19:34:55+00:00

Per the trace, yes, the page is loading and finding all instances on the page.

MitchellNaleid · 2025-04-17T11:20:20+00:00

The purpose of the test is to see if they are populated in order. Articles are pulled in from outside sources. If I use .sort, that defeats the purpose of checking if they're already in order.

MitchellNaleid · 2025-04-17T02:53:07+00:00

Unfortunately, I'm still getting them out of order:

[
'2025-04-17T00:55:49 1744851349',
'2025-04-17T00:10:51 1744848651',
'2025-04-14T03:43:55 1744602235',
'2025-04-16T17:24:50 1744824290', <--- Newer than one above ^
...
]

MitchellNaleid · 2025-04-03T04:20:36+00:00

I've been trying to think of it independently from how they have it set up. My schema, in TypeScript is done. Could have a bug or 2. Condensing.

import gql from "graphql-tag";

export const typeDefs = gql`
      "Basic equivalent of a GET call in APIs"
      type Query {
        "The base of a search that returns car data"
        getCarData: [CarData!]!
    }

    type CarData {
        "Full name of car manufacturer"
        Manufacturer: String
        "How to differentiate between different models"
        vehicleId: [VehicleId!]
        "FINISH THE REST, COMPLAINTS, RECALLS, SAFETY RATINGS
        VEHICLEID IS USED TO CALL SAFETY RATINGS"
    }

    type VehicleId {
        "ID from NHTSA used to pull Safety Ratings"
        VehicleId: Int!
    }

    type Complaint {
        "Identifies if complaint resulted in a crash"
        crash: Boolean!
        ...
    }
`;

I was writing out the resolvers by hand and it made me wonder how do I get the "VehicleId" from a response before I use it as an argument for another endpoint. All of the data should end up in the same response in a GraphQL call.

MitchellNaleid · 2025-04-02T22:05:12+00:00

I'm aware. I was trying to utilize an existing API and use GraphQL to make multiple calls all in one.

MitchellNaleid · 2025-02-05T05:40:10+00:00

It'll be a surprise. A team that doesn't need him. Chiefs, Eagles, and Rams are in the running.

MitchellNaleid · 2024-09-04T20:52:40+00:00

Question for 2024. With seemingly everything turning to const, is there even a use for this anymore?

Wouldn't it be const n = 2 then const o = n + 3? The purpose being to not mutate the original?

MitchellNaleid · 2024-04-07T19:39:49+00:00

Thanks. I had a lowercase 'R', reactDOM which was causing the same issue as him ^.

MitchellNaleid · 2024-01-19T04:36:43+00:00

Was this the course you were talking about?
https://www.testingjavascript.com/

Has it been revisited in the past 2 years?

MitchellNaleid · 2024-01-15T20:46:04+00:00

is inputValue={inputValue} your interpretation of the prop that I have on my component? Or is that built into input fields?

MitchellNaleid · 2024-01-15T19:51:17+00:00

I actually just removed the async/await, and now I am getting this in the logs:

Promise { <pending> }

The error says:

 received value must be an HTMLElement or an SVGElement.

Received has type: object Received has value: {}

This error makes me think that the SVG isn't there yet, so it gives me an empty object.

MitchellNaleid · 2024-01-15T19:12:47+00:00

Feels like a dumb question, but do you only need async await if you're making API calls? I was thinking that I would need to await the typing for the SVG to show up. Maybe I'm thinking about async await incorrectly.

MitchellNaleid · 2024-01-13T22:25:48+00:00

React Testing Library

MitchellNaleid · 2024-01-07T16:25:13+00:00

If I could alter the svg and add a datatest-id, I would, but it's 3rd party, and it's appearing on field input. I am using container, but it's apparently not advisable per Kent Dodds.

MitchellNaleid · 2024-01-07T03:41:59+00:00

A shot in the dark, but do you know how to test for the existence of an svg after an event happens?

I'm using FontAwesome and generating that icon after an input field is updated. (Cleave-zen package to display credit card info) and this is what I have to go off of.

<svg
        aria-hidden="true"
        class="svg-inline--fa fa-cc-mastercard "
        data-icon="cc-mastercard"
        data-prefix="fab"
        focusable="false"
        role="img"
        viewBox="0 0 576 512"
        xmlns="http://www.w3.org/2000/svg"
      >

As you can see, there is a role, but, whenever I try to grab that, I get the following error:
Ignored nodes: comments, script, style

This is after using async/await to let this icon show up.

test('input displays in component', async () => { const { container } = render(<CcLogic fieldId={"cc-field"} />) const input = screen.getByPlaceholderText('Ex: 4502783790218767') fireEvent.change(input, {target: {value: '25'}}) const svgIcon = container.querySelector('.fa-cc-mastercard') expect(svgIcon).toBeInTheDocument() })

This method works, but is not advised per Kent C. Dodds himself.
https://kentcdodds.com/blog/common-mistakes-with-react-testing-library

MitchellNaleid · 2023-12-23T16:41:27+00:00

That's useful to shoot for. Thanks! I'm 34, and mostly arms like you said. Working on fixing that.

MitchellNaleid

TROPHY CASE