Skip to content

feat: Take down steep issues from 522 to 104 #571

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

Merged
merged 23 commits into from
Apr 7, 2025

Conversation

aguspe
Copy link
Contributor

@aguspe aguspe commented Aug 3, 2024

Description

This PR is the third PR in our efforts to bring full RBS support to the ruby_lib_core

A lot of support RBS files from Selenium, should be deleted after the Selenium RBS files are available with the gem

We will probably need 2 or 3 extra PRs to add full support, so it will be easier for @KazuCocoa to review, once we managed to get this merged, I will start working on the next PR.

And the results might be affected by the steep upgrade by dependabot here #601.

The end goal is to be able to run type validation on the CI pipeline.

Before the PR:

Screenshot 2024-07-24 at 20 37 43

After the PR:

Screenshot 2024-08-03 at 20 25 26

Motivation and Context

We want to add type support to the core library as specified here #296 so it's easier for new contributors to understand what the methods are expecting and returning.

We also want eventually to be able to run automatic type checks to avoid type errors, and we would like for the RBS files to serve as documentation so the contributors do not need to write as many comments and speed up their flow.

@aguspe aguspe changed the title feat: Take down steep issues from 522 to 427 feat: Take down steep issues from 522 to 286 Sep 14, 2024
@aguspe aguspe changed the title feat: Take down steep issues from 522 to 286 feat: Take down steep issues from 522 to 163 Sep 15, 2024
@aguspe
Copy link
Contributor Author

aguspe commented Sep 15, 2024

@KazuCocoa just to let you know I'm still working on this, sorry to trigger the tests so often, is there a way that I could run the pipeline only when the draft is done?

Thanks and have a great weekend

@KazuCocoa
Copy link
Member

Yea, you could comment out triggers in .github directory until you're ready

@KazuCocoa
Copy link
Member

Especially functional-test.yml

@aguspe aguspe changed the title feat: Take down steep issues from 522 to 163 feat: Take down steep issues from 522 to 104 Sep 25, 2024
@aguspe aguspe marked this pull request as ready for review April 6, 2025 09:41
@aguspe aguspe requested a review from KazuCocoa as a code owner April 6, 2025 09:41
Copy link
Member

@KazuCocoa KazuCocoa left a comment

Choose a reason for hiding this comment

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

lgtm in my best knowledge. Thank you!

@KazuCocoa KazuCocoa merged commit 9b138d6 into appium:master Apr 7, 2025
25 of 27 checks passed
@aguspe
Copy link
Contributor Author

aguspe commented Apr 10, 2025

Great thank you @KazuCocoa I will create another PR from master to continue the steep work, thanks!

@KazuCocoa KazuCocoa added the size:M contribution size: M label May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:M contribution size: M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants