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

Query organization on dev.to/api #9212

Closed
gixxerblade opened this issue Jul 8, 2020 · 9 comments
Closed

Query organization on dev.to/api #9212

gixxerblade opened this issue Jul 8, 2020 · 9 comments
Assignees
Labels
area: API api or request related issues area: organizations external contributors welcome contribution is welcome!

Comments

@gixxerblade
Copy link

Feature Request

Currently there in no way to query an organization on dev.to/api

Describe the solution you'd like

It would be nice to query https://dev.to/api/organization/articles, https://dev.to/api/organization/users, https://dev.to/api/organization/listings where organization is e.g., https://dev.to/api/vetswhocode

The description could read:

This endpoint allows the client to retrieve an organization .

"Organizations" is all the data that an organization creates on DEV that typically show up in the feed and a user is connected >to. They can be a blog post, a discussion question, a help thread etc. but is referred to as an organization within the code.

By default it will return featured, published articles ordered by descending date of publication

It supports pagination, each page will contain 30 articles by default.

@rhymes
Copy link
Contributor

rhymes commented Jul 9, 2020

Thanks for the issue! We'll take your request into consideration and follow up if we decide to tackle this issue.

To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @thepracticaldev/oss and we will follow up within 3 business days.

For full info on how to contribute, please check out our contributors guide.

@rhymes
Copy link
Contributor

rhymes commented Sep 28, 2020

I think the URL structure should be something like:

dev.to/api/organizations/{org_username}/articles and so on

If someone tackles this I strongly recommend to send separate PRs for each endpoint and keep the API spec file updated as well.

@twinsfan421
Copy link
Contributor

I can work on this

@rhymes
Copy link
Contributor

rhymes commented Sep 29, 2020

I've assigned you the issue, thanks @twinsfan421 !

@twinsfan421
Copy link
Contributor

@rhymes I am working on it and have couple questions.
In addition to the articles, users and listings, should I make a show action like dev.to/api/organizations/{org_username} for just the organization's info?
Should there be any authentication for these endpoints?
Thanks

@citizen428
Copy link
Contributor

In addition to the articles, users and listings, should I make a show action like dev.to/api/organizations/{org_username} for just the organization's info?

Yes, that's probably a good idea. It should mirror https://docs.dev.to/api/#operation/getUser.

Should there be any authentication for these endpoints?

Rough rule of thumb that the current API seems to follow: if it's public information, no authentication is needed. Best to follow similar API endpoints for now, the API docs are a good reference for this: https://docs.dev.to/api/

@cmgorton
Copy link
Contributor

cmgorton commented Feb 2, 2021

Hey @twinsfan421 thanks so much for all the contributions to this so far. Given the current PRs that have already been merged is there anything else left for this issue?
We recently implemented a new internal RFC process for feature requests. With this new process we are figuring out when a Forem team member or a community contributor should work on a feature request.

I don't want to pull you off of this issue if you are close to finishing up any other tasks.

@twinsfan421
Copy link
Contributor

Hey @twinsfan421 thanks so much for all the contributions to this so far. Given the current PRs that have already been merged is there anything else left for this issue?
We recently implemented a new internal RFC process for feature requests. With this new process we are figuring out when a Forem team member or a community contributor should work on a feature request.

I don't want to pull you off of this issue if you are close to finishing up any other tasks.

This issue is completed. Thank you

@cmgorton
Copy link
Contributor

cmgorton commented Feb 2, 2021

Thanks for the confirmation and thanks again for all the work you did on this. We really appreciate it 🙏🎉

@cmgorton cmgorton closed this as completed Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: API api or request related issues area: organizations external contributors welcome contribution is welcome!
Projects
None yet
Development

No branches or pull requests

5 participants