massive-com / massive-com/client-jvm
Is this client being actively maintained?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 38
- Avg merge
- 32m
- Merged PRs (30d)
- 2
Description
I see the last release was cut in January, however there are a lot of issues raised for mismatch from the open api spec.
I also see that when I fetch get_v2_reference_news, the open api spec has an insights block which I do not see in the client API. Want to know if I should be rolling my own client at this point.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the client representation for get_v2_reference_news and comparing it with the referenced OpenAPI definition, especially the insights block. Confirm whether the client exposes that block and document the resulting maintenance or implementation gap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100