coreConvention
commented
1 year ago We use it in an extremely complex json-schema/ui-schema/formly reactive forms configuration based questionnaire-like form generator because it allows me to individually define things in a single ui-schema. For example:
Json-Schema
{
type: "object",
properties: {
someproperty: {
type: "string"
}
}
}Ui-schema:
{
scope: "#",
formlyConfig: {
templateOptions: {
fxLayout: "row wrap
}
}
}
{
scope: "#/properties/someproperty",
formlyConfig: {
templateOptions: {
fxFlex: 50,
fxLayoutAlign="end center"
}
}
}I removed a lot of stuff for the example but you can hopefully see the correlation, I think. Alot of the above stuff is programatically generated from configuration in a mongo database, using a very complex json merging scheme.
Which then applies the necessary css to both the element generated by formly as well as the wrappers formly generates by adding the directives in the formly custom field types:
<div
[fxLayout]="to.fxLayout ?? 'row wrap'"
[fxLayoutAlign]="to.fxLayoutAlign ?? ''"
[fxLayoutGap]="to.fxLayoutGap ?? '1rem grid'"
>
<ng-container *ngFor="let f of field.fieldGroup; trackBy: trackById">
<formly-field [fxFlex]="getFlex(f)" [field]="f"></formly-field>
</ng-container>
</div>
Without this it would be almost impossible because some of the wrappers/parent elements formly generates can't be affected directly without parsing and validating existing classes applied to the elements. And doing some fancy pseduo class css magic that defeats the purpose of being able to apply it with just the json.
This is a bit of an oversimplification but without flex-layout this is going to be EXTREMELY difficult. Not all of the customizations can just be applied via css classes, as both formly and flex-layout use both the class and style attributes on the fly to do their magic and deal with the outer and inner elements where they are applied. Applying the flex css itself wouldn't be super difficult, its what the directives themselves do that makes this work, not just the css.
@DuncanFaulkner I would likely be willing to chip in on maintenance as well. As you can see from the above explanation I have a vested interest in seeing this project continue. I will end up having to write my own directives otherwise, which I will do if I have to, but this is such a great package I would rather continue using it lol!
jpike88
PeterNSkovgaard
aceArt-GmbH
DuncanFaulkner
runeabrahams1
michaelfaith
Anthony-Wratpor
In accordance with the announcement in the Medium post about this library's future, this is a tracking issue for requesting assistance in migrating complex usages of Angular Layout.
If you believe that your library falls under this case, you can request (or vote on existing) migration guides to other, supported solutions like Tailwind or Angular CDK.
Please use the +1 reaction wherever applicable, and do not comment +1. Those comments will be ignored/deleted.
I appreciate your patience as we go through this process. Until the campaign is complete, the library will still be actively maintained.
In your request, please include the following details:
This will help us prioritize the guides as they are submitted.