![]() ![]() The package.json can probably be used for this purpose. The big question here is how to 'package' that version of the repo into a set of docs so that while you are switching between them it isn't always jumping to latest. The version will be from available versions, not sure how to deduce this entirely yet. The app will have the ability to choose a repository and also choose a version. Once the files are on the CDN the CDN needs CORS enabled. Since blob storage doesn't support directories the files will be named to simulate that like so - dependency-injection/0.5.0/doc/api.json It will have a parent container aurelia that holds each blob. The azure blob storage will be set up in a similar fashion, but changed slightly. An optional modifier would be a specific version like gulp push-docs-to-azure -v 0.5.2 in case it isn't the most recent version you are pushing. There will be an additional new gulp task gulp push-docs-to-azure or something similar. Once the release is ready the task will run. The current doc generation task needs to be altered to match the above output at time of release. Inside will be the docs, api.json, and package.json files. If you deviate from the conventions, then you probably know enough to do so. I think this is OK to have as a black box as long as devs follow whatever conventions are recommended. I know a lot of effort is being put into this, along with some feature requests for the package manager. ![]() (If there are multiple end states in Aurelia using different technologies, then show multiple conversions) I would love to see a video of the Welcome/Flickr sample app converted from Durandal to Aurelia. TypeScript, ES6, Traceur, Babel (6to5), transpiler - What are all these? Are they required? What are my options? Upgrading a Durandal app to Aurelia will probably touch on some of these. Is that type of process even supported with Aurelia? I'm thinking "no" since Aurelia has a more building-block architecture, and these tools aid in pulling in what is needed, as well as providing other services. Node/gulp/jspm - What are these, how to set them up, and use them during the dev process? In Durandal (using VS) I could just download the latest release, copy the js files into my project and I'm off coding (look mom, no Node!). Depending on who the upcoming books/courses are targeted to, this may give ideas on what to have as prerequisites or have some initial coverage on, especially if targeted towards beginners. For experienced JS devs most of these are part of your everyday toolbox. Here's a short list of things I've noted that I may need to become more knowledgeable in when I upgrade to Aurelia. As I've been following this group and the progress of Aurelia, I'm discovering there are a lot more technologies/tools involved outside of the framework itself. Really the only thing I spent some extra time on was learning about require.js/r.js for build/bundle options. ![]() I knew some JS (very limited) before Durandal, but Durandal "just worked" and very easy to setup. I posted this on the Aurelia gitter forum, and was asked by jdanyow to re-post it here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |