Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow setting top-level options for IgniteUI components
See original GitHub issueIt would be great if the following syntax is supported by IgniteUI components:
<ig-grid [(dataSource)]="ds" [height]="h" [width]="w"></ig-grid>
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
IgxColumnComponent | Ignite UI for Angular
Defined in projects/igniteui-angular/src/lib/grids/columns/column.component.ts:248. Sets/gets whether the column is filterable. Default value is true . let ...
Read more >igZoombar Integration with Custom Components - Ignite UI
Assigning the custom provider is done through the provider option. By default igZoombar will create an instance of $.ig.ZoombarProviderDataChart to interface ...
Read more >igniteui-angular2
All top level options are allowed to be set as attributes of an Ignite UI control custom tag. In this case options attribute...
Read more >Angular Data Grid Part II: Get started in 5 steps | Ignite UI
In Part I of the “Using Angular Data Grid” with Ignite UI post, ... the options of the menu you can find the...
Read more >Python - Tkinter Toplevel
Your application can use any number of top-level windows. Syntax. Here is the simple syntax to create this widget − w = Toplevel...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top level-options would be nice for controls like comboboxes but I think for the grid it wouldn’t help much because most of the configuration is done on the sub levels. Why was this possible in Angular 1 and not now? Because the scope is now missing? Would it be possible to define the columns as child components? I’m struggling a lot with how to move my Angular 1 stuff to Angular 2 especially with your grid for which I modified your original wrapper. For example I wanted button columns that were able to call a function in Angular and with your help was able to do this using $compile when the column was rendered. Now there is no $compile so I’m kind of stuck. Also as in your example setting the header text would be important to enable localization. Are you having the same troubles and maybe can help to solve them?
Hi, in our opinion this is a must have feature because we would like to put UI layout stuff into the HTML where we think it belongs. If you specify all your options in the code you break the separation and basically don’t need the HTML anymore. Also I think the sample as it is now is incomplete because we would like to also have the column definitions and feature settings in HTML just like it was possible with the AngularJS wrapper for Ignite UI. So for example as the first AngularJS sample:
<ig-grid id="employees-grid" data-source="employees" primary-key="productID" auto-generate-columns="false"> <columns> <column key="employeeID" header-text="ID" width="65px" data-type="number"></column> <column key="lastName" header-text="Last Name" width="250px" data-type="string"></column> <column key="firstName" header-text="First Name" width="200px" data-type="string"></column> <column key="title" header-text="Title" data-type="string"></column> </columns> </ig-grid>Do you plan to implement this feature because otherwise we will have to look for other solutions? Thanks and best regards.