Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dot Notation Access for API Response Handling #56

Open
abhi1693 opened this issue Dec 24, 2023 · 0 comments
Open

Dot Notation Access for API Response Handling #56

abhi1693 opened this issue Dec 24, 2023 · 0 comments
Labels
status: available No one has claimed responsibility for resolving this issue. type: feature New feature or request

Comments

@abhi1693
Copy link
Contributor

py-jelastic version

0.0.4

Jelastic version

8.4.1

Feature type

New functionality

Proposed functionality

The addition of a feature to convert dictionaries to objects with dot notation access in py-jelastic would enhance the flexibility and readability of the code when managing Jelastic environment configurations. The feature would involve creating a new utility class within py-jelastic that can recursively convert dictionaries into objects. This class should be able to handle nested dictionaries and convert them into nested objects, providing a clean and Pythonic way to access response keys. It should also include error handling to manage attempts to access keys that do not exist.

Use case

This feature would be beneficial for py-jelastic users who prefer object-oriented access to configurations rather than dictionary-based access, which can be verbose and error-prone when dealing with deeply nested structures. For instance, users managing complex configurations with multiple nested parameters would find it easier to read and write config.database.host instead of config['database']['host']. This can also reduce the likelihood of typos and runtime errors due to incorrect key access, thus improving the overall reliability of configuration management within the py-jelastic framework.

External dependencies

No response

@abhi1693 abhi1693 added type: feature New feature or request status: available No one has claimed responsibility for resolving this issue. labels Dec 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: available No one has claimed responsibility for resolving this issue. type: feature New feature or request
Development

No branches or pull requests

1 participant