Init

Author: MikeBild

.gitignore

@@ -0,0 +1,3 @@
+.DS_Store
+node_modules
+npm-debug.log

.npmignore

@@ -0,0 +1,5 @@
+.DS_Store
+node_modules
+npm-debug.log
+examples
+test

.prettierrc

@@ -0,0 +1,5 @@
+{
+  "bracketSpacing": false,
+  "eslintIntegration": true,
+  "singleQuote": true
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at go@linklet.run. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Linklet Contributor Guide
+
+Excited about Linklet and want to make it better? We’re excited too!
+
+Linklet is build for developers just like you, striving to create tools and libraries around HTTP based Microservices. We welcome anyone who wants to contribute or provide constructive feedback, no matter the level of experience. If you want to help but don't know where to start, let us know, and we'll find something for you.
+
+Here are some ways to contribute to the project, from easiest to most difficult:
+
+* [Reporting bugs](#reporting-bugs)
+* [Improving the documentation](#improving-the-documentation)
+* [Responding to issues](#responding-to-issues)
+* [Bug fixes](#bug-fixes)
+* [Suggesting features](#suggesting-features)
+
+## Issues
+
+### Reporting bugs
+
+If you encounter a bug, please file an issue on GitHub via the repository. If an issue you have is already reported, please add additional information or add a 👍 reaction to indicate your agreement.
+
+While we will try to be as helpful as we can on any issue reported, please include the following to maximize the chances of a quick fix:
+
+1. **Intended outcome:** What you were trying to accomplish when the bug occurred, and as much code as possible related to the source of the problem.
+2. **Actual outcome:** A description of what actually happened, including a screenshot or copy-paste of any related error messages, logs, or other output that might be related.
+3. **How to reproduce the issue:** Instructions for how the issue can be reproduced by a maintainer or contributor.
+
+Creating a good reproduction really helps contributors investigate and resolve your issue quickly.
+
+### Improving the documentation
+
+Improving the documentation, examples, and other open source content can be the easiest way to contribute to the library. If you see a piece of content that can be better, open a PR with an improvement, no matter how small! If you would like to suggest a big change or major rewrite, we’d love to hear your ideas but please open an issue for discussion before writing the PR.
+
+### Responding to issues
+
+In addition to reporting issues, a great way to contribute to Linklet is to respond to other peoples' issues and try to identify the problem or help them work around it. If you’re interested in taking a more active role in this process, please go ahead and respond to issues.
+
+### Bug fixes
+
+For a bug fix change (less than 30 lines of code changed), feel free to open a pull request. We’ll try to merge it as fast as possible and ideally publish a new release on the same day. The only requirement is, make sure you also add a test that verifies the bug you are trying to fix.
+
+### Suggesting features
+
+Most of the features in Linklet came from suggestions by you! We welcome any ideas about how to make Linklet better for your use case.
+
+### Code review guidelines
+
+Here are some things we look for:
+
+1. **Required CI checks pass.** This is a prerequisite for the review, and it is the PR author's responsibility.
+2. **Simplicity.** If there are too many files, redundant functions, or complex lines of code, suggest a simpler way to do the same thing. In particular, avoid implementing an overly general solution when a simple, small, and pragmatic fix will do.
+3. **Testing.** Do the tests ensure this code won’t break when other stuff changes.
+4. **No unnecessary or unrelated changes.** PRs shouldn’t come with random formatting changes, especially in unrelated parts of the code.
+5. **Code has appropriate comments.** Code should be commented, or written in a clear “self-documenting” way.
+
+## New contributors
+
+If you want to contribute to Linklet, but aren't quite sure where to start, take a look at the [roadmap and design docs](docs/ROADMAP.md). Just pick one of the upcoming features that you're interested in, and start working on it. If the design doc isn't clear enough (which it probably won't be), open an issue thread so we can discuss it.

ISSUE_TEMPLATE.md

@@ -0,0 +1,8 @@
+# Intended outcome:
+What you were trying to accomplish when the bug occurred, and as much code as possible related to the source of the problem.
+
+# Actual outcome:
+A description of what actually happened, including a screenshot or copy-paste of any related error messages, logs, or other output that might be related.
+
+# How to reproduce the issue:
+Instructions for how the issue can be reproduced by a maintainer or contributor.

LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2017 CodeCommission / Mike Bild
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -0,0 +1,29 @@
+# Linklet Higher-Order HTTP Handler
+
+## Documentation
+
+* [Linklet Microservice Documentation](https://github.com/CodeCommission/linklet/tree/master/docs)
+* [Linklet Examples](https://github.com/codecommission/linklet-examples)
+* [Introduction to NodeJS](https://github.com/mikebild/introduction-nodejs)
+
+## How to use it in my project?
+
+Being stable and inventive and have a look to our [Linklet examples](https://github.com/codecommission/linklet-examples).
+
+## Contributors
+
+Every participation is welcome, just read [CONTRIBUTING](CONTRIBUTING.md) and make your first PR!
+
+## Issue Reporting
+
+If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public [GitHub issue tracker](https://github.com/codecommission/linklet-higher-handlers/issues).
+
+## License
+
+This project is licensed under the MIT license. See the [LICENSE](LICENSE) file for more info.
+
+## Thanks
+
+You like this and you want to see what coming next? Follow us on Twitter [`@linklet_run`](https://twitter.com/linklet_run).
+
+Enjoy!

lib/index.js

@@ -0,0 +1,2 @@
+module.exports.withParams = require('./with-params');
+module.exports.withRoute = require('./with-route');

lib/with-params.js

@@ -0,0 +1,29 @@
+const url = require('url');
+const pathToRegexp = require('path-to-regexp');
+
+module.exports = ({path}) => handler => (req, res) => {
+  req.hasParamMatch = false;
+  const uri = url.parse(req.url, true);
+  const paramKeys = [];
+  const pathMatchingPattern = pathToRegexp(path, paramKeys);
+
+  const isPatternMatchesPath = pathMatchingPattern.exec(
+    req.url.replace(uri.search, '')
+  );
+
+  if (!isPatternMatchesPath) return handler(req, res);
+  if (!isPatternMatchesPath.length) return handler(req, res);
+
+  req.hasParamMatch = true;
+  const paramValues = isPatternMatchesPath.splice(
+    1,
+    isPatternMatchesPath.length - 1
+  );
+
+  req.params = paramKeys.reduce((state, next, idx) => {
+    state[next.name] = paramValues[idx];
+    return state;
+  }, {});
+
+  return handler(req, res);
+};