Use stack exchange api for questions #417
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tfoote
approved these changes
Sep 9, 2024
There was a problem hiding this comment.
This is a much better approach. We inherited the rss from Askbot, but the direct API access is much better to take advantage of now that we've switched over.
I don't have a checkout handy to validate this, but since it's already completely broken, I'll put this in and we can iterate from there.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #354
I switched to the questions API, and the CORS issues go away.
I modernized the js, but also did not try to duplicate the previous "descriptions" functionality. The user can just go to the Stack Exchange site if they are interested.