# Mustafa7 - @Abse currently footprinter supports...

Channel: #contributor
Source: https://discord.com/channels/1233487248129921135/1540307169075924992
Started: 2026-08-21T10:30:47.303000+00:00
Last activity: 2026-08-21T10:58:55.248000+00:00

## Mustafa7 — 2026-08-21T10:30:46.631000+00:00

<@398467566588264449> currently footprinter supports params like `w` `h` for passives but there are courtyards being generated for custom footprinter strings for passives and also easyeda imports(string like `res_p4.6599mm_pw2.91mm_ph2.9106mm`) doesnt describe the w/h in the passives strings. So is that an intendted behaviour or is that an issue. if its an issue then there are two repos needs fixing, 
1. tscircuit/footprinter should be able to produce courtyards from w/h params
2. circuit-json-to-footprinter should describe strings like `res_p4.6599mm_pw2.91mm_ph2.9106mm_w10mm_h5mm` from the easyeda data.

## Abse — 2026-08-21T10:33:01.265000+00:00

I'm not sure if all footprints need w and h?

## Mustafa7 — 2026-08-21T10:33:02.864000+00:00

[attachment]
Attachment: Screenshot_2026-08-21_at_4.02.51_PM.png — https://community.tscircuit.com/media/1540307740176420954

## Abse — 2026-08-21T10:33:27.383000+00:00

Yes all footprints need to generate courtyard

## Abse — 2026-08-21T10:33:51.273000+00:00

How the footprints that has courtyard is doing it?

## Mustafa7 — 2026-08-21T10:36:14.264000+00:00

it uses direct footprint: 
```<resistor
      name="R_PD_GATE_DRIVE"
      resistance="22k"
      footprint="0603"
      pcbX={-27.5}
      pcbY={26.7}
      pcbRotation={90}
      schX={10}
      schY={4}
      schSheetName={sheets.powerInput}
      schSectionName={sections.usbPd}
    />```

## Mustafa7 — 2026-08-21T10:36:51.684000+00:00

for custom footprinter strings for passives there are no couryards being generated

## Mustafa7 — 2026-08-21T10:38:15.515000+00:00

this is the one that does not have a courtyard from the image:
```export const B5819W_SL = (props: DiodeProps) => {
  const { name = "D1", ...restProps } = props

  return (
    <diode
      name={name}
      pinLabels={pinLabels}
      supplierPartNumbers={{
  "jlcpcb": [
    "C8598"
  ]
}}
      manufacturerPartNumber="B5819W SL"
      footprint="res_p3.4mm_pw1.2mm_ph0.95mm"
      cadModel={{
        objUrl: "https://modelcdn.tscircuit.com/easyeda_models/assets/C8598.obj?uuid=e9d505c99b6c436aaf827a29c5ba4f84",
        stepUrl: "https://modelcdn.tscircuit.com/easyeda_models/assets/C8598.step?uuid=e9d505c99b6c436aaf827a29c5ba4f84",
        pcbRotationOffset: 0,
        modelOriginPosition: { x: 0, y: 0.000012699999999199463, z: -0.6 },
      }}
      {...restProps}
    />
  )
}```

## Abse — 2026-08-21T10:43:17.578000+00:00

Wr can just calculate the courtyard internally no need to add w and h for all right?

## Abse — 2026-08-21T10:44:21.192000+00:00

In cases like this <@757706909351411845> should see this too footprinter should follow a clear API design

## Mustafa7 — 2026-08-21T10:53:06.611000+00:00

but wouldnt that be a hack to guess courtyards from the pads width/height?

## Mustafa7 — 2026-08-21T10:53:49.614000+00:00

Body will be different from pads right

## Anas — 2026-08-21T10:58:43.109000+00:00

Seve and I noticed that too; we did try to do some PRs, like extracting the courtyard size from the silkscreen
CC: <@757706909351411845>

## Mustafa7 — 2026-08-21T10:58:55.248000+00:00

https://github.com/tscircuit/footprinter/pull/818
https://github.com/tscircuit/circuit-json-to-footprinter/pull/105
Codex did something