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

Improve documentation for weather API client #63

Open
cwasicki opened this issue Dec 22, 2023 · 1 comment
Open

Improve documentation for weather API client #63

cwasicki opened this issue Dec 22, 2023 · 1 comment
Assignees
Labels
part:❓ We need to figure out which part is affected priority:high Address this as soon as possible type:enhancement New feature or enhancement visitble to users
Milestone

Comments

@cwasicki
Copy link
Contributor

cwasicki commented Dec 22, 2023

What's needed?

We decided to progress fast on the client implementation #62 and update documentation in a subsequent PR.

FYI @noah-kreutzer-frequenz

Proposed solution

No response

Use cases

No response

Alternatives and workarounds

No response

Additional context

No response

@cwasicki cwasicki added part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed type:enhancement New feature or enhancement visitble to users labels Dec 22, 2023
@cwasicki
Copy link
Contributor Author

cwasicki commented Sep 2, 2024

@noah-kreutzer-frequenz Has this been done?

@cwasicki cwasicki added this to the v1.0.0 milestone Sep 10, 2024
@TalweSingh TalweSingh added priority:high Address this as soon as possible and removed priority:❓ We need to figure out how soon this should be addressed labels Sep 23, 2024
@TalweSingh TalweSingh self-assigned this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:❓ We need to figure out which part is affected priority:high Address this as soon as possible type:enhancement New feature or enhancement visitble to users
Projects
None yet
Development

No branches or pull requests

3 participants