Skip to content

feat(server): take stopped/started state into account in completions#332

Merged
kangasta merged 2 commits intomainfrom
feat/server-completion-state
Oct 8, 2024
Merged

feat(server): take stopped/started state into account in completions#332
kangasta merged 2 commits intomainfrom
feat/server-completion-state

Conversation

@scop
Copy link
Copy Markdown
Member

@scop scop commented Sep 19, 2024

We could add some more to avoid various other completions for servers let's say in maintenance state, but this covers the most common cases for now.

@scop scop requested a review from a team as a code owner September 19, 2024 08:04
Copy link
Copy Markdown
Contributor

@villevsv-upcloud villevsv-upcloud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! A short changelog entry would be useful.

I'll create a separate PR to accommodate the unrelated linter issues, so this branch can be rebased after that been merged to main.

@kangasta kangasta force-pushed the feat/server-completion-state branch from 00e7888 to 4c858f7 Compare October 8, 2024 13:56
@kangasta kangasta merged commit c03bbbb into main Oct 8, 2024
@kangasta kangasta deleted the feat/server-completion-state branch October 8, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants