<div align="center">

slinky

<a href="https://discord.gg/BmnxRpbt53"><img alt="Slinky Discord Server" src="https://img.shields.io/discord/918997996660740157?style=flat" /></a> <img alt="GitHub" src="https://img.shields.io/github/license/paulo-e/slinky" /> <img alt="GitHub issues" src="https://img.shields.io/github/issues/paulo-e/slinky" />

<a href="https://www.codefactor.io/repository/github/paulo-e/slinky"><img alt="CodeFactor" src="https://www.codefactor.io/repository/github/minsk-dev/slinky/badge"/></a> <a href="https://github.com/paulo-e/slinky/actions/workflows/main.yml"><img alt="GitHub Actions" src="https://github.com/paulo-e/slinky/actions/workflows/main.yml/badge.svg"/></a>

Library for quick development in Spring Boot using Java Generics and Reflection.

</div>

---

Why "slinky"?

<a href="https://en.wikipedia.org/wiki/Slinky"> <img align="right" width="40%" src="https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/2006-02-04_Metal_spiral.jpg/800px-2006-02-04_Metal_spiral.jpg" alt="A slinky (toy)"> </a>

A slinky is a precompressed helical spring toy invented by Richard James in the early 1940s. And "Spring" is the framework that this library is built upon.

But why use slinky?

The (java!) generic classes slinky provides are going to allow developers to create Spring Boot applications at record speed.

What slinky provides to every resource?

Currently, slinky provides GET, POST, PUT, DELETE, PATCH, HEAD and OPTIONS for resource(s) gathering(s). Right now we only operate in REST but adding RESTful classes to inherit from is on the todo list.