MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Real-time_Edge-Aware_Image_Processing_with_the_Bilateral_Grid",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "653": {
                "pageid": 653,
                "ns": 0,
                "title": "React (JavaScript library)",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "\n==Components==\nComponents are reusable pieces of jsx which depend on some input properties and get rerendered whenever those properties change.\n\nReact has two types of components: function components and class components (those which extend React.Component).\nHistorically, class components were used for components with state and function components were stateless.\nToday, function components can also have state using hooks and should be preferred for new code.\n\n===Function components===\n\n====State====\nhttps://beta.reactjs.org/learn/managing-state\nState can be managed in several ways:\n* [https://beta.reactjs.org/reference/react/useState <code>useState</code>] allows you to define a state variable, similar to a class property, which will trigger a rerender.\n* [https://beta.reactjs.org/reference/react/useReducer <code>useReducer</code>] allows you to refractor state manipulation to a separate ''reducer'' function outside of your component.\n* [https://beta.reactjs.org/reference/react/useEffect <code>useEffect</code>] allows you to setup and remove listeners. These always run on the client in SSR variants of React.\n* Contexts\n* [https://beta.reactjs.org/reference/react/useRef#useref <code>useRef</code>] returns a reference to an object with a <code>current</code> parameter which allows you to have state without rerendering.\n\nEvery time any properties or state changes, your function component will be rerendered.\nTherefore, you cannot rely on local variables to hold their state.\nAdditionally, you must call <code>useState</code> identically across renders (i.e. not conditionally), ideally near the top of your function.\n\nNote that the state of the function is tied to their position in the React virtual dom.\nA single component rendered multiple times will have different state.\n\n==Frameworks==\n===Next.js===\n[[Next.js]] allows you to use React with server-side rendering.\n\n==Resources==\n* [https://reactjs.org/tutorial/tutorial.html React tutorial]"
                    }
                ]
            },
            "797": {
                "pageid": 797,
                "ns": 0,
                "title": "Reading Papers",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Things to look for when reading papers.\n\n==How I read papers==\nI'm not very experienced but here is how I read papers:\n\n* Watch their video.\n** Their video will give a high-level summary. Usually video explanations are faster/easier to understand.\n** Sometimes they show their results. Pay attention to problems in their results.\n** If they don't have a video, look for a third-party one on YouTube.\n* Read the abstract.\n* Look through all figures and captions.\n* Read the Intro and Methods.\n** Tells you the problem they're addressing and their approach to addressing it.\n** What is the input to and output of their pipeline?\n* Read the Related Works section.\n** This gives you an idea of what others have tried. Especially important if you don't work in the field.\n* Read the Evaluation section.\n** Usually this is just a bunch of tables and numbers but it can give you links to datasets and a reference for some benchmarks.\n** This is important if you plan on building upon the work.\n\n==Resources==\n* [https://www.youtube.com/watch?v=Uumd2zOOz60 Yannic Kilcher How I Read a Paper]"
                    }
                ]
            }
        }
    }
}