{"_id":"560093933aa0520d00da0bdf","__v":8,"githubsync":"","category":{"_id":"562d68d5d38b650d0044472a","project":"56000f0d8c0c9d0d00dcad21","__v":5,"version":"56000f0e8c0c9d0d00dcad24","pages":["562d904026a0a10d00ad6c30","56398e44a19edf0d009721a7","5639e5bad25e8919005f3e6a","563a30e3a19edf0d009722e6","563bf349d8f2d20d00448b39"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-10-25T23:42:13.718Z","from_sync":false,"order":1,"slug":"getting-started","title":"Getting Started"},"project":"56000f0d8c0c9d0d00dcad21","user":"56000e979e7ccf0d000a1e66","version":{"_id":"56000f0e8c0c9d0d00dcad24","project":"56000f0d8c0c9d0d00dcad21","__v":13,"createdAt":"2015-09-21T14:07:10.176Z","releaseDate":"2015-09-21T14:07:10.176Z","categories":["56000f0e8c0c9d0d00dcad25","56008f2497f69f1700f21a36","560091601503430d007cc936","560e0d8054af2b0d005bbe92","560e3ce7ad6b200d00ff471c","560e3cf2c4e4ae0d00b42ed1","561c81d0e822e12b00e1fe00","561c81e9e822e12b00e1fe01","561c823d20b4a92b007d5147","56257f8951bf1c0d001f660a","562d5f165bd25e0d0054dbd4","562d68d5d38b650d0044472a","56421aebb0dc090d00f88438"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-09-21T23:32:35.250Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"While it's possible to use Space without adopting the *Flux* and/or *Event Sourcing* patterns, it's highly recommended you at least consider Flux for managing the state of your app given we believe it's a good for most projects.\",\n  \"title\": \"Will I benefit from using Space without adopting a specific pattern?\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Flux\"\n}\n[/block]\nmeteor add space:flux\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Event sourcing infrastructure\"\n}\n[/block]\nmeteor add space:event-sourcing\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Testing Package\"\n}\n[/block]\nTesting is a major focus for the Space project and is in fact one of the primary reasons for it to exist. Space abstracts the boilerplate and exposes convenient and expressive BDD APIs to allow for simple and rock solid testing of module and application code.\n\n**Get started**\nAdd `space:testing` to your Package.onTest in the package.js\n\nSince your app is written into code we can provide nice BDD style APIs to test it, with much less boilerplate and time wasted second guessing your tests. Maybe it's actually less code overall!\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Package-only architecture\",\n  \"body\": \"Space currently only supports testing of package code since it uses practicalmeteor:munit under the hood, an extension of Meteor's own package testing solution TinyTest. This may seem like a limiting factor, but it's recommended practice when building a system with Space.\"\n}\n[/block]","excerpt":"","slug":"installation","type":"basic","title":"Installation"}
[block:callout] { "type": "info", "body": "While it's possible to use Space without adopting the *Flux* and/or *Event Sourcing* patterns, it's highly recommended you at least consider Flux for managing the state of your app given we believe it's a good for most projects.", "title": "Will I benefit from using Space without adopting a specific pattern?" } [/block] [block:api-header] { "type": "basic", "title": "Flux" } [/block] meteor add space:flux [block:api-header] { "type": "basic", "title": "Event sourcing infrastructure" } [/block] meteor add space:event-sourcing [block:api-header] { "type": "basic", "title": "Testing Package" } [/block] Testing is a major focus for the Space project and is in fact one of the primary reasons for it to exist. Space abstracts the boilerplate and exposes convenient and expressive BDD APIs to allow for simple and rock solid testing of module and application code. **Get started** Add `space:testing` to your Package.onTest in the package.js Since your app is written into code we can provide nice BDD style APIs to test it, with much less boilerplate and time wasted second guessing your tests. Maybe it's actually less code overall! [block:callout] { "type": "info", "title": "Package-only architecture", "body": "Space currently only supports testing of package code since it uses practicalmeteor:munit under the hood, an extension of Meteor's own package testing solution TinyTest. This may seem like a limiting factor, but it's recommended practice when building a system with Space." } [/block]