Unexpected behavior when using both resolved and unresolved params

[CharlesRngrd]

dlt version

1.6.0

Describe the problem

Hi,

In the resource bellow, I define 3 kings of params:

• pagination param
• resolved param
• unresolved param

{
    "name": "users",
    "selected": False,
    "endpoint": {
        "path": "/api/v4/users",
        "paginator": {"type": "page_number", "total_path": "totalPages"},
        "params": {
            "sortBy": "hiringDate",
            "desc": True,
            "displayArchivedUsers": False,
            "id_cofaq": {
                "type": "resolve",
                "resource": "companies",
                "field": "id",
            },
        },
        "data_selector": "content",
    },

},

The issue is that the unresolved params are not sent to the request according to the logs:

https://api.eurecia.com/eurecia/api/v4/users with params={'id_cofaq': 'COFAQ--------20191114-164321', 'page': 0}

Could you fix this please ?

Expected behavior

No response

Steps to reproduce

Create a fake resource with both:

• pagination param
• resolved param
• unresolved param

Then run the resource and see in the logs which parameters are there.

Operating system

Windows

Runtime environment

Local

Python version

3.12

dlt data source

No response

dlt destination

No response

Other deployment details

No response

Additional information

No response

[burnash]

Hey @CharlesRngrd thanks for reporting this. Looking into it.

[burnash]

@CharlesRngrd thanks again for reporting this issue. Unfortunately have to revert the related PR in 37f3d45 and publish dlt version 1.6.1 without this feature on PyPI. I've added some regression tests in #2268. Once we merge it we'll continue working on the features implemented in #2208

[CharlesRngrd]

Ok no problem.
I hardcoded the parameter so I can wait.