Is the resource Angular Data Grid: Group Cell Renderer, free for commercial use?
I ask because in the documentation it is explicit that for the refusal to work it is necessary to import the package from the ag-grid enterprise, and if I remove it does not work.
// app/app.component.ts (QUESTION IMPORT)
import 'ag-grid-enterprise';
Yes it is required to import ag-grid enterprise to use Angular Data Grid: Group Cell Renderer
Related
I'm trying to use the ImageList component. I imported it as follows:
import { ImageList} from "#material-ui/core";
This works just fine. When I add the "variant" prop to the component, however, I start getting errors saying that I'm not matching any of the overloads. I see the variant prop used in their demos and on the API reference.
Error message
I suspect this has something to do with versioning -- I read something about ImageList being MUI v5 alpha. If that's the case I don't know what to do to fix my issue. The linker is finding the module just fine, so I don't know what's wrong.
I think I answered this myself. I was importing from the v4 version of MUI (#material-ui/core). I had to install v5 and import from here, instead:
import ImageList from '#mui/material/ImageList';
And then the variant prop worked. I was disheartened to find out that breakpoint props don't exist with this component, like they do with Grid. Instead, I had to use MUI's useMediaQuery hook to get the screen size and set the col prop accordingly.
I am trying to add ag multi column filter, https://www.ag-grid.com/javascript-data-grid/filter-multi/
But getting the following warning ag-Grid:
Looking for component [agMultiColumnFilter] but it wasn't found.
You have to check your license key added properly.
Multicolumn filter supports with AG Grid Enterprise version not with Community.
https://www.ag-grid.com/angular-data-grid/licensing/
import {LicenseManager} from "ag-grid-enterprise";
LicenseManager.setLicenseKey("license-key");
We've recently gone through an upgrade of ag-grid-react to version 23.0.0 and have enabled charting, but I've noticed that we don't have the chart toolbar rendered under the hamburger menu as it would be in the demos. I've imported/configured the grid as follows:
import 'ag-grid-enterprise/dist/styles/ag-grid.css';
import 'ag-grid-enterprise/dist/styles/ag-theme-balham-dark.css';
import 'ag-grid-enterprise';
import { AgGridReact } from 'ag-grid-react';
// ... component definition things as referenced in props below
<AgGridReact
defaultColDef={columnDefs.defaultColDef}
columnTypes={columnDefs.columnTypes}
columnDefs={cols}
rowData={rows.length ? rows : null}
enableRangeSelection
groupMultiAutoColumn
groupDefaultExpanded={2}
groupHideOpenParents
suppressAggFuncInHeader
resizable
sortable
animateRows
pivotMode={prefs.pivotMode}
suppressLoadingOverlay
statusBar={this.state.statusBar}
onGridReady={this.onGridReady}
autoGroupColumnDef={{ cellRendererParams: { suppressCount: true } }}
getContextMenuItems={this.getContextMenuItems}
enableCharts
/>
Screenshot of result: The toolbar renders, but we don't have the menu to change data/settings along the right hand side that are found in the Documentation and demos. I'm not sure if I'm missing something in the configuration of the grid, or if I'm missing some chart-specific imports. Any help would be appreciated!
Found the solution on my own, in our package.json there was a conflicting style included from an older ag-grid that was conflicting with the styles
After update from v3 to v4.8.3 do not work customizing components. My goal is to override Select component to get text color 'red'.
const styles = theme => ({ temp: { fontSize: 12, color: "red" })
...
<Select classes={{ root: classes.temp }} ....> ...</Select>
but MuiInputBase-input class always stay on top.
https://i.imgur.com/JGK7J89.png
I see that there are diffrents in styles loading by html head import, my current version(v4) is:
https://i.imgur.com/gAlECET.png
I see that import is doubled, and overrides my custom style.
On v3 all mui styles imports was placed on top of list and not mixed vs custom styles. I cant find more info to get solution and reason of doubling imports. where error may arise?
edit:
i must give some more details...
Problem appered after a big legacy project was updated. For represet my problem, i cut most of code and create demo on codesandbox .
Unfortunately it work fine on codesandbox, and dont let see a problem. if i download zip and start it - i have my problem. Tried on two machine ubuntu 18.04 and MacOS, both have that problem - colour red dont applied to second select. Some more detail are in issue if it will helpfull for someone. Reason in solution below
I have created sandbox for you where you can see the overwritten menu items.
Code sandbox: https://codesandbox.io/s/override-select-component-material-ui-c1io6?fontsize=14&hidenavigation=1&theme=dark
The reason was that nested component has wrong import statement. Wrong import that was work "properly" in v3 for some reason:
import InputBase from "#material-ui/core/InputBase/InputBase";
must be:
import InputBase from "#material-ui/core/InputBase";
becouse it, my styles was overriding by base style
I have 2 ag-grid table components in my project with each of them having their own export and excel styles(numberformat, bold etc., ).
If I export the table ag-grid-1 and then export table ag-grid-2 (or vice versa) then some of the stylings(like numberformatting, bold etc.;) from ag-grid-1 styles are getting applied to the data of ag-grid-2.
Below are the steps mentioning when the styling gets overridden and when it doesn't
Styling gets Overridden:
Step 1: open the application and export table ag-grid-1.
Step 2: export table ag-grid-2.
-Styling of ag-grid-2 excel export overridden by styling of ag-grid-1.
Styling doesn't get Overridden:
Step 1: open the application and export table ag-grid-1.
Step 2: Reload application.
Step 3: Export table ag-grid-2.
-Styling of ag-grid-2 doesn't get overridden and stays as we defined.
Is there anyway to solve this?
Expected result: exporting of one table shouldn't override the styling of another table export.
For your issue, you must install the new version of ag-grid. They addressed this issue (AG-2981) with a fix on v21.0.0. The excel export styles sheets are not being cleared when there is two tables on the same page with export capabilities.