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

[Bug]: Metadata is incorrect for various functions #666

Open
cursive-ide opened this issue Feb 28, 2024 · 0 comments
Open

[Bug]: Metadata is incorrect for various functions #666

cursive-ide opened this issue Feb 28, 2024 · 0 comments
Labels
bug Something isn't working triage

Comments

@cursive-ide
Copy link

What version of Datahike are you using?

0.6.1558

What version of Java are you using?

17

What operating system are you using?

MacOS

What database EDN configuration are you using?

N/A

Describe the bug

A Cursive user has filed cursive-ide/cursive#2880, because Cursive can't see the Datahike API due to the fact that it's generated at runtime via introspection, and Cursive uses static analysis. Cursive has a solution for that via stub generation, but when I implement that for Datahike I get arity errors using common functions in the API (e.g. d/transact and d/q). This is because those functions have their arglists incorrectly specified in their metadata, which Cursive uses to generate the stubs. This will also affect generated API documentation and the like, and probably clj-kondo also.

What is the expected behaviour?

The arglists should correctly specify the expected parameters in the metadata.

How can the behaviour be reproduced?

Use (meta #'d/transact) or (meta #'d/q), and observe that the arglists meta doesn't match the examples in the actual function documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

1 participant