Going to v1.0

[savente93]

This discussion thread is both for tracking and discussing issues relating to what would be necessary for moving hydromt to v1.0. Discussions can happen below but I think the best course of action is to edit this top comment with things that are agreed upon
Given that we have a milestone for this now I think it's bet to just refer to that and not duplicate the bookkeeping. However I'll leave this topic open to serve as a point of discussion

[savente93]

To kick off, I think that all current deprecation warnings should be removed. Things that currently carry a deprecation warning should be removed, or the deprecation warning should be removed, and support should be added permanently(ish). Things that pop ino my head that need a decision are:

• support for ini files
• the use of the alias in the data catalog
• data catalog dictionary like features

I'll see if I can search the codebase for more in a while. feel free to add ones that you're aware of or think should be added to the pile

[savente93]

Some other options ones that are currenly makred as deprecated in the code base:

• Using outlet as kind in setup_region
• the staticmaps property of the model class
• the *_staticmaps functions
• the *_staticgeoms functions
• defining regions based on static maps
• test_model_api
• the gaguemap method
• bashin_shape
• storage_options in driver_kwargs
• pasing kwargs into adapters instead of driver_kwargs
• adding predeined data catalogs as key-word arguments
• from_artifacts
• the root & catagory key outside of the meta key
• kind=outlets in basin_mask
• within stream argument in basin_mask

[savente93]

In the absence of any objections I've just started to make issues to keep track of everything, but I'm not totally up to date on all the things mentioned so the issues will probably need further refinement/rewording