Kedro is an open-sourced Python framework for creating maintainable and modular data science code.

Kedro

Hi team
We found an issue with how Kedro handles empty runtime parameters when triggered from Airflow.
In our pipeline config, we have something like:
```some_dataset:
  type: spark.SparkDataset
  file_format: delta
  filepath: "gs://&lt;bucket-prefix&gt;${runtime_params:env}-dataset/app_usages"```
Airflow correctly sends an *empty string (`''`)* for the `env` parameter,
but Kedro interprets it as *`None`*.
So the final path becomes:
```gs://&lt;bucket-prefix&gt;None-dataset/```
instead of:
```gs://&lt;bucket-prefix&gt;-dataset/```
Here’s the simplified Airflow call:
```"params": build_kedro_params(
    [
        f"project={get_project_id()}",
        f"env={env_param}",  # env_param = ''
        
    ]
)```
It looks like Kedro converts empty strings from runtime parameters into `None` during parsing.

*Has anyone else run into this issue with Kedro interpreting empty strings as `None`?*

A workaround could be to use a <https://docs.kedro.org/en/1.0.0/configure/advanced_configuration/#how-to-use-custom-resolvers-with-omegaconfigloader|custom resolver>.

```custom_resolver = {"env_param": lambda env_param: env_param if env_param else ""}```