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

fix incorrect typings for compile get/set methods #58

merged 1 commit into from Jan 21, 2022


Copy link

@haakemon haakemon commented Jan 21, 2022

The previous PR (#54) was closed on incorrect assumptions. I added a comment on it, but got no response, so I hope a new PR is fine. We use this library, and the incorrect typings are annoying and I would like to see it fixed :)

So, let me try and clear up the confusion from the previous PR:

There is a get ( function that accepts 2 parameters, and
there is a set ( function that accept 3 parameters

Additionally, on the compile object
there is also a get ( method that accepts 1 parameter, and
there is also a set ( method that accepts 2 parameters.

Currently in the typings, both variants accept 2 and 3 parameters, which is incorrect.

This is also demonstrated in the tests, f.ex here: and here, on the compile object where only 1 parameter is used for get: and 2 parameters is used for set:

This PR fixes the incorrect typings for the get/set methods on the compile object.

Thanks for the great library, I hope you will consider accepting this fix :)

Copy link

marcbachmann commented Jan 21, 2022

This looks good. Thanks for bringing this up again.

@marcbachmann marcbachmann merged commit b8e1e6a into janl:main Jan 21, 2022
5 checks passed
Copy link

marcbachmann commented Jan 22, 2022

I'd like to release that once #50 gets merged

@haakemon haakemon deleted the fix-typings branch Jan 22, 2022
Copy link
Contributor Author

haakemon commented Jul 13, 2022

Hi @marcbachmann , would it be possible to get this released without waiting for #50? There has not been any progress on that issue for some months now, and this typing issue is still bugging me 🙂

This was referenced Jul 13, 2022
Copy link

marcbachmann commented Jul 13, 2022

Released as v5.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants