René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat(http): accept string for method in RequestOptions class and interface","articleBody":"Currently, the method must be of the `ResponseMethods` TypeScript enum, which is really an integer. So to create a request in TypeScript, one would use the enum to describe the method instead of passing in the method string:\n\n``` typescript\nvar options = new RequestOptions({\n  url: '/foo.json',\n  method: RequestMethods.POST\n});\nvar request = new Request(options);\n```\n\nThis adds some convenience for TypeScript and Dart users to get some IDE/compiler help to make sure the method is a valid value. But plain old ES5 users probably don't want to pass `0` as the method value. Instead, `RequestOptions` should have the `method` property be a union type of `RequestMethods | string`, and should validate the provided string \u0026 throw if not a recognized method.\n\nI'm not sure `Request` class needs to accept method as a string though. Ideally, we could reduce instances of type ambiguity to public APIs.\n","author":{"url":"https://github.com/jeffbcross","@type":"Person","name":"jeffbcross"},"datePublished":"2015-07-01T23:53:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/2840/angular/issues/2840"}