Timeline for Javascript RegEx match URLs for tokens extraction
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2019 at 9:38 | vote | accept | Daniele | ||
| May 5, 2016 at 10:19 | comment | added | Daniele | @Flambino I know there is URL parsing in Node, but if you read the code you will notice that my requirement is a little far from parsing the url, I need to exctract specific values separated in different ways | |
| May 5, 2016 at 3:41 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 1 character in body; edited title
|
| May 5, 2016 at 3:17 | answer | added | Laurel | timeline score: 2 | |
| S Apr 20, 2016 at 14:24 | history | bounty ended | CommunityBot | ||
| S Apr 20, 2016 at 14:24 | history | notice removed | CommunityBot | ||
| Apr 12, 2016 at 20:33 | history | edited | 200_success |
edited tags
|
|
| S Apr 12, 2016 at 20:28 | history | edited | Sjoerd Job Postmus | CC BY-SA 3.0 |
improved formatting of URL.
|
| Apr 12, 2016 at 20:24 | review | Suggested edits | |||
| S Apr 12, 2016 at 20:28 | |||||
| Apr 12, 2016 at 15:33 | comment | added | Flambino | Even without npm, there's URL parsing built into Node already, so there's no need to roll your own | |
| Apr 12, 2016 at 14:16 | comment | added | Zack | Have you looked into a library to do this? It seems like it would be more effective than reinventing your own. I found gist.github.com/jlong/2428561 and npmjs.com/package/url-parse in the first few search results. Even if you can't use them, you can look over the code base and see if anything can be used with what you have. The second link specifically mentions a RegEx engine. | |
| S Apr 12, 2016 at 12:47 | history | bounty started | Daniele | ||
| S Apr 12, 2016 at 12:47 | history | notice added | Daniele | Draw attention | |
| S Apr 7, 2016 at 13:01 | history | edited | BCdotWEB | CC BY-SA 3.0 |
fixed a typo
|
| S Apr 7, 2016 at 13:01 | history | suggested | José Castro | CC BY-SA 3.0 |
fixed a typo
|
| Apr 7, 2016 at 12:57 | review | Suggested edits | |||
| S Apr 7, 2016 at 13:01 | |||||
| Apr 6, 2016 at 7:11 | comment | added | michael.zech | The line "const path_matcher = /(?:([^\/\/]+))/g;" : Wouldn't have '/(?:([^\/]+))/g' the same result. You add the slash ( / ) two times to your set of not allowed characters. The second time isn't necessary. At least I guess so? I can be wrong ... | |
| Apr 5, 2016 at 9:34 | history | asked | Daniele | CC BY-SA 3.0 |