Collaborating on some new features?

[matthewstern]

Mike,

Thanks for your work on blsAPI. Incredibly useful. I've developed for my own purposes a bit of code that simplifies (I think) the way blsAPI is called, and how it outputs data. It internalizes the creation of the 'payload' and returns data in wide format. Additionally, I have borrowed code from walkerke's tidycensus package that stores a user's BLS API key in the .Renviron rather than passing it into every call.

My code is here. Is integrating this kind of functionality into blsAPI interesting to you?

[mikeasilva]

@tallishmatt - I would be happy to collaborate. I am pursuing a graduate degree currently so I have limited bandwidth. The only requirement is that backwards compatibility will need to be retained as others are using the package. If you would submit a pull request with your additional feature add I would be happy to accept it.

[adhi-r]

I'm subscribed to this thread somehow so pardon my jumping in. But I had noticed that Michael had stopped maintaining this package (and had assumed it was because he was busy with something - grad school is as good an excuse as any haha). In particular, there was/is an issue with how this package handled the "Note" section of the API results, breaking the data frame in the end. I ended up coming across a package called "blscrapeR" which is more actively maintained and has a ton of nice convenience features. It also leverages the latest in tidyverse ideology. I would recommend checking out that package before setting out on a revamp of this package.

…

On Thu, Nov 28, 2019 at 5:29 PM Michael Silva ***@***.***> wrote: @tallishmatt <https://github.com/tallishmatt> - I would be happy to collaborate. I am pursuing a graduate degree currently so I have limited bandwidth. The only requirement is that backwards compatibility will need to be retained as others are using the package. If you would submit a pull request with your additional feature add I would be happy to accept it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28?email_source=notifications&email_token=ADJ4HDZ2RWDPSRLN2SXP6ATQV6XDHA5CNFSM4JPUN77KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFMMR3A#issuecomment-559466732>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJ4HD2UDNNJXJXIWXNX4ATQV6XDHANCNFSM4JPUN77A> .