Skip to content
This repository has been archived by the owner on Nov 9, 2018. It is now read-only.

JS Implementation + Test Structure #13

Open
niemyjski opened this issue Feb 28, 2015 · 1 comment
Open

JS Implementation + Test Structure #13

niemyjski opened this issue Feb 28, 2015 · 1 comment

Comments

@niemyjski
Copy link
Member

I took a look at the csla.js file and it had tests and a bunch of stuff into it. Yet there is also a test project. I like what a lot of projects are doing and that is placing a .spec.js file right next to the file that contains the tests. This tests right next to the file and the tooling can pick it up via a wild card. Also, It's kind of hard to track what's transpiled and what isn't when viewing the source.

@niemyjski niemyjski changed the title Structure JS Implementation + Test Structure Feb 28, 2015
@niemyjski
Copy link
Member Author

Typically in our projects where we used typescript we only included typescript and out build would output it to a dist folder for release. I think we should follow the same conventions. For example (we are not using ts here), one of my projects (https://github.com/exceptionless/Exceptionless.UI/tree/master/src) we only check in the actual source. The build/ci server would run grunt / gulp build and put a package out there on bower /npm for people to download.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant