Skip to content

refactor(api)!: renamed getCurrent functions to avoid ambiguity#10229

Merged
amrbashir merged 4 commits into
devfrom
refactor/api/get-current-abiguity
Jul 11, 2024
Merged

refactor(api)!: renamed getCurrent functions to avoid ambiguity#10229
amrbashir merged 4 commits into
devfrom
refactor/api/get-current-abiguity

Conversation

@amrbashir
Copy link
Copy Markdown
Member

closes #10193

@amrbashir amrbashir requested a review from a team as a code owner July 9, 2024 12:44
Comment thread .changes/get-current-ambguity.md
@FabianLars
Copy link
Copy Markdown
Member

I dislike this so much as a Rust dev 😭

Copy link
Copy Markdown
Contributor

@Legend-Master Legend-Master left a comment

Choose a reason for hiding this comment

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

Should we also change getAll to getAllWindows etc?

Also probably need to update examples

@sanbei101
Copy link
Copy Markdown

That's a really good idea

@amrbashir
Copy link
Copy Markdown
Member Author

Should we also change getAll to getAllWindows etc?

Also probably need to update examples

done

Copy link
Copy Markdown
Member

@FabianLars FabianLars left a comment

Choose a reason for hiding this comment

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

Just making github acknowledge Tony's review

@amrbashir amrbashir merged commit 2b1ceb4 into dev Jul 11, 2024
@amrbashir amrbashir deleted the refactor/api/get-current-abiguity branch July 11, 2024 11:26
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.

[feat] Distinct names for all the different getCurrent functions in the frontend API

4 participants