Change this repository name

[mrgzi]

Now that we have added the CSS Grid feature in this PR and we need to change this repository name.

According to me, the most suitable name for this repository is "angular/ui-layout"

[CaerusKaru]

Personally, my vote is for @angular/layout because it seems more to-the-point. But if the community feels a certain way, I'll leave this thread here as a means to vote.

If we get enough votes either way, this is definitely something we can run up to the Core team.

[julianobrasil]

I'd go with @angular/layout too.

[d2kx]

I don't really care about names myself, but we'd have

@angular/layout using stuff from @angular/cdk/layout then. Looks weird, and will raise the question for new users why those are seperate, even though the LayoutModule in the CDK is a different beast.

Also, and I know this is unrelated, we need to promote this package a lot better. It's getting really old telling users on the angular2 subreddit and elsewhere that "use Bootstrap because Angular and Angular Material don't have layout functionality" about this one.

[CaerusKaru]

@d2kx I usually draw the comparison between @angular/animations and @angular/platform-browser/animations. One is clearly a utility for animations, and one is a utility to help construct animations (ie one is higher-level, and one is lower-level).

I agree it may be confusing for some, but before we make any change, we'll make sure to well document it. (Not to mention that in the material2 README, the section on layout already links here instead of to the CDK. I get the feeling that a lot of people don't even realize it's a thing).

Re promotion, we can definitely launch an awareness campaign if/when the name for the package changes, or after ng-conf if it doesn't (to promote the new Grid functionality). As it is, this package is already pretty popular. Although we don't have nearly the same functionality, we're about half the size of Material in terms of downloads.

[bardiel]

+1 To @angular/layout; IMHO.

To me as a user, it wouldn't look weird at all that @angular/layout would be using stuff from the "Component Development Kit"'s layout module. Semantically, actually, makes perfect sense. =P

[d2kx]

But here's the thing: people that like the CDK-Layout functionality like BreakpointObservers etc. to do Mobile/Desktop layout switcheroo already have

import { LayoutModule } from '@angular/cdk/layout';

in their app.module.ts today. If flex-layout renames to @angular/layout, and there will be a meta module to import both flex and grid modules, it would surely also be LayoutModule as the exported name. But we can't import two "LayoutModule".

Sounds picky, but this is not an unlikely thing to happen.

[julianobrasil]

Doesn't it make sense to have different modules (FlexLayoutModule and GridLayoutModule) instead of just one (LayoutModule)? @angular/forms works like this (FormsModule and ReactiveFormsModule).

[CaerusKaru]

@d2kx Ah, I see your concern. Thankfully, with the advent of scoped injectables in Angular v6, the LayoutModule in @angular/cdk/layout is an empty shell and doesn't need to be imported for use (see here). It will likely be removed in a minor release after v6 final.

Since @angular/layout would likely debut as compatible with Angular v6, I don't see an issue.

@julianobrasil We already have scoped modules like that FlexModule and GridModule, but we also bundle everything into the top-level for those who want everything at once (similar to the old MaterialModule)

[CaerusKaru]

@MGazi42 How are you measuring that? While the number of votes is helpful, it's really entirely up to the Angular Core team. We're in discussions with them, and will update here when we have something. In the meantime, for those just reaching this issue, adding to the vote total will only help the cause.

[yehia123]

I agree, the name makes it sound it strictly uses FlexBox. Kind of sad i just discovered this awesome library. Love it tho, thank you!

[probert94]

I would go with @angular/layout too and I don't think it is confusing.
As much as I know it is using (or will be using) @angular/cdk/layout under the hood.
That means it isn't different from @angular/material/table, which is using @angular/cdk/table.
However, I would preffer to see this library as part of the CDK itself sometimes.
@angular/material itself references this repository as it's layout implementation, so I would like to see a closer collaboration between the 2 libraries.

[kuncevic]

Does renaming will be taking place soon closer to RC release or something?