Stamplay is a new JavaScript-centric BaaS (backend as a service), ideal for Ember developers.
ember-stamplay is a work-in-progress Ember addon aiming at providing first-class support for Stamplay.
We rely on Ember Data, Ember Simple Auth and Stamplay's REST API. We do not use Stamplay's JS SDK.
⚪ -- not implemented yet, planned
⚪❔ -- WTF is that even? Not counted as a missing feature
🔘 -- in progress (leaf) or partially implemented (branch)
⚫ -- implemented
⚫❔ -- implemented but some edge cases might be missing
⛔ -- won't implement, not counted as a missing feature
- 🔘 Basic documentation in this readme
- ⚫ Intro
- ⚫ Roadmap
- ⚪ Changelog
- ⚪ Installation and setup
- ⚪ Working with one-way relationships
- ⚪ Document code using YUIDoc
- ⚪ Build YUIDoc API website
- 🔘 Auth
- ⚫ Email/password authentication
- ⚫ Email/password signup
- ⚫ Social OAuth authentication/signup
- ⚫ Ember Data authorization
- ⚫ AJAX authorization
- ⚫ Logout
- ⚪ Password editing
- ⚪ Password recovery
- 🔘 Working with models
- ⚫ CRUD for object models
- ⚫ GET objects
- ⚫ GET object
- ⚪❔ GET User's Objects
- ⚪❔ GET Object Activity
- ⚫ POST object (create)
- ⚫ PUT object (update)
- ⛔ PATCH object (partial update) -- not implementing due to how Ember Data is designed
- ⚫ DELETE object
- 🔘 CRUD for user model
- ⚫ GET users
- ⚫ GET user
- ⚫ GET user status (checks session, returns user model for JWT token)
- ⚪ GET following
- ⚪ GET followed_by
- ⚫ POST user
- ⚪ PATCH role
- ⚫ PUT user
- ⚪ PUT follow
- ⚪ PUT unfollow
- ⚫ DELETE user
- ⚪ Roles
- ⚪ GET roles
- ⚪ GET role
- Stripe
- ⚪ Subscription
- ⚪ GET subscriptions
- ⚪ GET subscription
- ⚪ POST subscription (create)
- ⚪ PUT subscription (update)
- ⚪ DELETE subscription
- ⚪ Card
- ⚪ GET card
- ⚪ POST card
- ⚪ Customer
- ⚪ POST customer
- ⚪ Charge
- ⚪ POST charge
- ⚪ Subscription
- ⚫❔ One-way relationships
- ⚫ Depagination for
findAll()andquery() - ⚫❔ Filtering and sorting via
query(), advanced queries with?where= - ⛔ Selecting attributes for lighter responses (might work out of the box, though)
- ⚪ Social actions
- ⚫ CRUD for object models
- ⚪ POST email
- ⚪ POST code block (run)
- ⚪ Social actions
- ⚪ Mixin for POST methods
- ⚪ Figure out where to perform GETting soical actions & where to store
- ⚪ A dummy app with the most basic use cases
- ⚪ Set up Mocha and Chai
- ⚪ Set up Mirage
- ⚪ Set up Travis CI build
- ⚪ Acceptance tests
- ⚪ Auth
- ⚪ Email/password authentication
- ⚪ Email/password signup
- ⚪ Social OAuth authentication/signup
- ⚪ Ember Data authorization
- ⚪ AJAX authorization
- ⚪ Logout
- ⚪ Password editing
- ⚪ Password recovery
- ⚪ Dummy app CRUD
- ⚪ Auth
- ⚪ Integration tests
- ⚪ CRUD for object models
- ⚪ GET objects
- ⚪ GET object
- ⚪❔ GET User's Objects
- ⚪❔ GET Object Activity
- ⚪ POST object (create)
- ⚪ PUT object (update)
- ⚪ DELETE object
- ⚪ CRUD for user model
- ⚪ GET users
- ⚪ GET user
- ⚪ GET user status (checks session, returns user model for JWT token)
- ⚪ GET following
- ⚪ GET followed_by
- ⚪ POST user
- ⚪ PATCH role
- ⚪ PUT user
- ⚪ PUT follow
- ⚪ PUT unfollow
- ⚪ DELETE user
- ⚪ Roles
- ⚪ GET roles
- ⚪ GET role
- Stripe
- ⚪ Subscription
- ⚪ GET subscriptions
- ⚪ GET subscription
- ⚪ POST subscription (create)
- ⚪ PUT subscription (update)
- ⚪ DELETE subscription
- ⚪ Card
- ⚪ GET card
- ⚪ POST card
- ⚪ Customer
- ⚪ POST customer
- ⚪ Charge
- ⚪ POST charge
- ⚪ Subscription
- ⚪❔ One-way relationships
- ⚪ Depagination for
findAll()andquery() - ⚪❔ Filtering and sorting via
query(), advanced queries with?where= - ⚪ Social actions
- ⚪ POST email
- ⚪ POST code block (run)
- ⚪ Social actions
- ⚪ Mixin for POST methods
- ⚪ Figure out where to perform GETting soical actions & where to store
- ⚪ CRUD for object models
For features you wish to see implemented, please visit linked issues and upvote!