Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JSON frontend support
See original GitHub issueHi, i love wttr.in and have been using it for a lot of personal projects lately. I believe wego supports JSON as an output (specified as a “frontend”, though I haven’t tested this personally). It would be awesome if wttr.in could support JSON output (or specifying any arbitrary frontend I suppose)… maybe something like:
GET /Buffalo- buffalo ny weatherGET /Buffalo?frontend=json- buffalo ny weather with-f jsonpassed to thewegocommand
There might need to be some extra processing by wttr.in to specify the appropriate headers to the requesting client to let it know the response is JSON.
If there is interest in this I can take a look at the code and see what I can do
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@xewl Yes, that’s true; thank you for reminding me of this issue. It is fixed now
There appears to be a solution built in: ?format=j1