Roadmap planning for MEAN.JS 0.5.0

[lirantal]

Features

• 0.4.0 - refactor_user 0.4.0 - refactor_user #559 (need PR work) added to backlog (mleanos)
• JWT (JSON Web Tokens) authentication method ([UNRESOLVED] JWT Authentication #1163) added to backlog (mleanos)
• Deprecating Grunt in favor of Gulp (deprecate(grunt): Remove Grunt #1175)
• Angular 1.4
• Angular Styleguide - https://github.com/johnpapa/angular-styleguide
  • Articles
  • Core (feat(core): Modify core module to implement style guidelines. #1202)
  • Users (feat(users): Modify users module to implement style guidelines. #1208)
• Articles admin feature #807 [Enhancement] Articles admin @ilanbiala

General Cleanups

• Cleaning up the /client issue 0.4 - favicon link in layout.server.view.html #608 ( @trainerbill )

Documentation

• Support deploying MEANJS to Cloud Foundry Support Deploying MEANJS To Cloud Foundry #681 support dropped & feature removed with chore(core): Remove Bluemix #1476 (mleanos)

[simison]

https://github.com/johnpapa/angular-styleguide #490

[utx0]

+1

[simison]

Supposing 0.5.0 won't hit the master branch very soon, we could try to include new ng-router. #530 once its ready/documented.

Using Angular 1.5 would be a good step towards 2.0 some time in the future (0.6.0?)

[pdfowler]

https://github.com/johnpapa/angular-styleguide #490

THIS!!!! Some key highlights that I've adopted in my project:

• "$scope must die!" - use controller as in place of $scope Y030:View Syntax, Y031:Controller Syntax and [Y032:with vm](https://github.com/johnpapa/angular-styleguide#style-y032]
• IIFE : Immediately Invoked Function Expressions Style Y010
• Standardized and rigorous use of JSHint, JSCS, JSDoc

[vaucouleur]

The edit and delete buttons, as well as the "posted on and posted by" at the bottom of every view-x.client.view.html pages are, arguably, a form of code duplication across generated modules.

Custom directives could help factoring out those pieces of code.

• On the Pros side, it would be pushing forward the "angular way" (directives), and help people get a concrete example of one or two simple custom directives.
• On the Cons side, it would make sites with a single "business object" module (Article), more complicated than necessary.

[ilanbiala]

@lirantal definitely a good idea to have many more directives implemented. Biggest thing is we should move to Angular 1.4 first.

[trainerbill]

I created a pagination directive to do paginiation + search easily (One directive and one view) like in the admin module:

https://github.com/trainerbill/mean/tree/PaginationDirective

We could use it across the entire app. I figure articles could benefit from it. Doesn't affect anything right now as it is just an unused directive. There is a POC on the homepage of that branch. Take a look and we can push it in if you want.

[simison]

Should this be divided into 0.4.x and 0.5.0 stuff (just subtitles, I don't mean having two separate issues) so that we'll have a better picture of the roadmap?

There's a number of PL's that might not be breaking and they could thus be pre-0.5.0.

[lirantal]

sure, I updated.

[roshangade]

+1 - really great features! Gulp, Angular 1.4, John Papa's Angular Styleguide