Improve handling of request field changes between versions
- Dominant language
- Python
- Stars
- 8
- Forks
- 7
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 23
Description
Low priority issue:
When an older request file is used with fields that are no longer used in the newer version of CDDS you're using:
```
[misc]
atmos_timestep = 900
use_proc_dir = True
no_overwrite = False
halo_removal_latitude =
halo_removal_longitude =
force_coordinate_rotation = False
```
It generates error messages which users may find a bit confusing:
```
cdds/common/request/misc_section.py", line 101, in from_config
return MiscSection(**values)
^^^^^^^^^^^^^^^^^^^^^
TypeError: MiscSection.__init__() got an unexpected keyword argument 'halo_removal_latitude'
```
It would be good to improve the way this is handled between versions to avoid these errors.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in cdds/common/request/misc_section.py at from_config, especially the MiscSection(**values) call, and trace how request fields are collected from the configuration. Determine how obsolete fields such as halo_removal_latitude are currently handled; done means older request files no longer produce the shown TypeError and instead receive clearer compatibility handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100