<@UHVDR4BNZ> It should match the number of args ok...

# http4k

[dave]

@Nezteb It should match the number of args ok. Can you post more of the code? (Including the full path)

[Nezteb]

[dave]

The sig of the function to create the handler only takes the path parts as args

[dave]

Where will the orgId and CWI come from?

[dave]

Guessing that the orgid is the path?

[Nezteb]

orgId will be in the path, CWI will be a JSON object in the Body. does the contract need to specify those before it can be mapped to the function?

[dave]

So it matches the greet example here. https://www.http4k.org/guide/modules/contracts/

[dave]

The path arg needs to be mapped in the spec. The body lens you will use manually to extract from the request

[dave]

If you want it to appear in the contract (OpenAPI) then it will also need to be added to the Meta block

[Nezteb]

Ohhhhh, I see. So body arguments are not taken as function arguments. They use lenses on the request.

[Nezteb]

except for Path/Query/Header params, correect?

[dave]

Only the path parameters make up that signature. The rest are retrieved.manually.

[dave]

(once again, this is down to the inability to create types with varying generic args)

[Nezteb]

Got it. That makes sense. 😄

[dave]

🙃