v0.6.3

See: https://github.com/sakuraapi/cli/milestone/11?closed=1

• Updated dependencies
• Now uses @sakuraapi/core@0.11.0
• Updated ConfigApi to take advantage of * routes
• Added unit test for ConfigApi
• Updated tests to deregister their dependencies after each test

v0.6.2

See milestone v0.6.2.

Bug fixes:

• #14 Comment correction
• #15 (EmailService spec was being included even if EmailService was not included)
• #16 SakuraApi/core@0.10.0 was not being properly referenced in the template for package.json

Contributors

• @CarsonF

v0.6.1

See: Milestone v0.6.1

Updated dependencies per #13.

v0.6.0

See milestone: v0.6.0

Template changes

• unhandledRejection and uncaughtException defaults now use LogService (see src/index.ts)

Dependency Updates

• v0.9.0 of @sakuraapi/api

v0.5.0

See: Milestone v0.5.0

Behold: Generating Models, Routables and Services

@Model, @Routable and @Injectable files can be scaffolded individually to save you the hassle of setting them up.

The example below assume you are in the root of your project's directory.

Currently, generated output still needs to be manually injected when you instantiate SakuraApi. Don't forget or it won't work.

Models

sapi g model src/models/SomeModel

This will create:

• src/models/some-model.ts
• src/models/some-model.spec.ts

Routables

sapi g routable src/api/SomeApi

This will create:

• src/api/some-api.ts
• src/api/some-api.spec.ts

Services (Injectables)

sapi g service src/services/SomeService

This will create:

• src/services/some-service.ts
• src/services/some-service.spec.ts

v0.4.0

sapi outdated - Keep your package.json dependencies up to date

Added sapi outdated to help you keep your sapi (and really any npm project) up to date.

Managing the never ending process of updating your package.json dependencies can be tedious. sapi outdated will take you through your list of outdated dependencies, giving you the option for each dependency to either skip it, update it to the wanted version, or updated it to the latest version. After each update, sapi runs npm test to make sure that particular update did not break your build. It also properly saves the new version in either dependencies or devDependencies in your package.json file. It's still a tedious process... but hopefully a little less so.

To get help with other options for outdated, use sapi outdated --help.

Refactor

Cleaned up the project layout and architecture a bit.

Debugging

Added a bunch of debug calls to make it easier to debug sapi in the future.

v0.3.0

Updated to support SakuraApi v0.8.0, auth-native-authority v0.3.0-13, and auth-audience v0.3.0.

Also added linting and fixed some bugs discovered along the way and added some comments to document output projects a bit better.

Implements #8

v0.2.0

New

• Issuer server now comes with an EmailService and a cleaner bootstrap process
• sapi is now a bit smarter about not including package.json dependencies that aren't being used for a particular server type

Bug fixes

• npm test wasn't working -- it does now

Updated dependencies

• debug from ^2.6.8 to ^3.1.0
• email-templates from ^2.6.0 to ^3.2.0

v0.1.0

Inaugural release of SakuraAPI Command Line Interface utility. It supports scaffolding three kinds of projects:

• basic servers with no authentication
• issuing authority server
• audience server