GithubHelp home page GithubHelp logo

igniteui / igniteui-react-examples Goto Github PK

View Code? Open in Web Editor NEW
11.0 34.0 5.0 31.76 MB

samples browser app and individual samples on how to use Ignite UI for React components

Home Page: https://infragistics.com/react-demos/samples

JavaScript 9.48% Batchfile 0.32% HTML 0.67% TypeScript 86.68% CSS 2.85%
react ingiteui-react ingiteui examples demos samples grids gauges maps spreadsheet

igniteui-react-examples's Introduction

ignite-ui

Examples of Ignite UI for React Components

This repository contains over 500 examples on how to use Ignite UI for React components:

Branches

NOTE: You should use master branch of this repository if you want to run samples on your computer. Use the vnext branch only when you want to contribute new samples to this repository.

Preview

You can preview and browse all samples in this repository by opening our React Samples Browser. Alternatively, you you can view these samples with detailed information in our React Help Documentation.

In addition, you can run each sample project individually from the ./samples folder or you can run from the ./browser folder to browse all samples in one website (see instructions below). You can run each sample on Code Sandbox website by clicking on the Edit Sandbox button in a readme file of sample project, e.g.

./samples/charts/category-chart/overview/README.md

Setup

To set up this project locally, clone this repository:

git clone https://github.com/IgniteUI/igniteui-react-examples.git

Running Individual Sample

  • check out the master branch

  • in VS Code, open a folder with existing sample, e.g.

./samples/charts/category-chart/axis-options/
  • type npm install --legacy-peer-deps command in terminal window

  • type npm run start command in terminal window

  • Wait until the build is completed and then open http://localhost:4200 in your browser.

At this point, you should see a website hosted example of Ignite UI for React component

Running All Samples

  • check out the master branch

  • open VS Code as Administrator

  • open the browser folder in this repository, e.g. C:\GitHub\igniteui-react-examples\browser

  • select View - Terminal menu item

  • type npm install --legacy-peer-deps command in terminal window

This will install required packages and Ignite UI for React packages

  • type npm run start command in terminal window to start this application locally

Note this application copies all individually sample projects from ./samples to ./browser/src folder when it is about to start running. Therefore, any changes to ./browser/src will be overridden on consecutive run of the application.

Wait until the build is completed and then open http://localhost:4200 in your browser. You should see a website with navigation menu for browning all samples in this repository.

SB Preview

Adding New Sample

  • create a new branch from the vnext branch

  • open a folder with existing sample, e.g.

./samples/charts/category-chart/axis-options/
  • copy the sample and rename the new folder, e.g.
./samples/charts/category-chart/axis-types/
  • open the newly created folder in VS Code

  • rename the .tsx file in src folder, using this naming convention:

ControlNameSampleName.tsx

./samples/charts/category-chart/axis-types/src/CategoryChartAxisTypes.tsx
  • open the .tsx file

  • rename class to the name of .tsx file

  • type npm install --legacy-peer-deps command in terminal window

  • type npm run start command in terminal window

  • implement the new sample in the .tsx file

  • close the new sample project in VS Code

  • delete node_modules folder in the new sample project

  • follow instructions in the next section

Verify New Sample

  • open the root folder of this repository in VS Code

  • type gulp updateSamples command in terminal window

NOTE this will re-generate the Readme.md file in the new sample

  • type npm run start command in terminal window

  • open http://localhost:4200 in your browser

  • verify that the new sample is listed in the navigation menu

  • verify that the new sample loads by clicking navigation link

  • verify that there are no errors in DEV console

  • take a screenshot of the new sample with navigation menu

  • commit your changes

  • create a pull request and target the vnext branch

  • paste the screenshot in you pull request

  • submit your pull request

Learn More

To learn more about Ignite UI for React components, check out the React documentation.

Updating Version of IgniteUI Packages

Perform these steps to update version of Ignite UI for React packages in all samples. NOTE that the order of these steps is very important.

  • open this repo in VS Code
  • open gulp-samples.js file
  • navigate to the updateIG function
  • change version of Ignite UI for React packages in the packageUpgrades array
  • open terminal window
  • run cd browser command
  • run gulp updateIG command
  • run npm install --legacy-peer-deps command
  • create pull request with your changes
  • open the Igniteui-xplat-example repo in VS Code
  • update version of Ignite UI for React packages in React template
  • create pull request with your changes in Igniteui-xplat-example repo

igniteui-react-examples's People

Contributors

agoldenbaum avatar astaev avatar azure-pipelines[bot] avatar chronossf avatar ddaribo avatar dependabot[bot] avatar dkamburov avatar georgianastasov avatar gmurray81 avatar hussar-mtrela avatar ig-robstoffers avatar igdivya avatar igmpeterson avatar iminchev64 avatar ivankitanov17 avatar kacheshmarova avatar kdinev avatar mayakirova avatar mddifilippo89 avatar mddragnev avatar pamelabrasil avatar parrnicholasj avatar rivaivanova avatar skrustev avatar teodosiah avatar turbobobbytraykov avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

igniteui-react-examples's Issues

Navigation Drawer samples issues

  1. The div element that has the onClick event handled to toggle the nav drawer menu has no size, so as the drawer is initially open, once clicked outside so it gets closed, it cannot be reopened again.
    (igniteui-react-examples\samples\menus\nav-drawer\add-drawer-items\src\index.tsx line 21)

image

Possibly toggle the drawer with a button, as in the Angular samples - https://www.infragistics.com/products/ignite-ui-angular/angular/components/navdrawer#angular-navigation-drawer-example

  1. Multiple nav drawer items can be active at a time, which is different than the WC and Angular samples behavior. Also, activating an item does not work in case the click is over the slotted icon or content elements of the drawer item.

  2. In the topic there is a 1px black border of the <div part="mini"> showing above the drawer:

image

1

Valid for Blazor and Web Components topics as well

Issue logged for WC samples - IgniteUI/igniteui-wc-examples#649
Issue logged for Blazor samples - IgniteUI/igniteui-blazor-examples#605

Update stepper animations sample

Stepper animations sample should be updated with the horizontalAnimation, verticalAnimation and animationDuration properties binding

Custom samples for React

  1. clipboard-operations - #325
  2. column-data-types - Ivan WIP
  3. conditional-cell-style-1 - IgniteUI/igniteui-xplat-examples#389
  4. custom-context-menu - #318
  5. data-paste-options - Topic that shows this is disabled for all platforms. Uses a custom directive in angular.
  6. data-searching - #314
  7. finjs - #372
  8. groupby-custom - #374
  9. groupby-styling - this should become a xplat sample: IgniteUI/igniteui-xplat-examples#213.
  10. infinite-scroll - #373
  11. multi-cell-selection-mode - #322
  12. row-drag-base - #375

Stepper Samples errors

The following errors are thrown when running the stepper samples against the latest igniteui-react verison "18.5.2-beta.2"

image

Add tick label

As Mr. DiFilippo pointed out in his support response I hearby open a feature request for IgrCategoryXAxis

Goal is to enable labels at the ticks - not in the middle of a bar in the IgrDataChart

All the best
Julian Wiche
Kriko Engineering

What we could consider adding is a tick label, which would completely separate from the axis label.

I would suggest submitting a new product idea here:
https://github.com/IgniteUI/igniteui-react-examples/issues

Michael DiFilippo
Software Developer
Infragistics, Inc.

Samples browser fails with eslint errors when compiling under a Japanese Windows OS

Use Windows with language and culture set to Japanese.
Do npm run build
The following errors appear:

Syntax error: Identifier expected (75:59)

src\samples\grids\grid\cell-editing-sample\WebGridCellEditSampleRoleplay.ts
Line 110:25: Irregular whitespace not allowed no-irregular-whitespace
Line 134:25: Irregular whitespace not allowed no-irregular-whitespace

src\samples\grids\grid\column-pinning-right-side\AthletesDataExtended.ts
Syntax error: ',' expected (2179:25)

src\samples\grids\grid\column-resize-styling\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\conditional-cell-style-1\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\conditional-cell-style-2\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\row-paging-basic\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\row-paging-options\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\toolbar-sample-1\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\toolbar-sample-2\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\toolbar-sample-3\AthletesData.ts
Syntax error: ',' expected (1333:25)

src\samples\grids\grid\toolbar-style\AthletesData.ts
Syntax error: ',' expected (1333:25)

Search for the keywords to learn more about each error.

React Grid examples don't add the CSS content in the samples metadata jsons

When the jsons for the code viewer metadata are created they all have this for the css file:

 {
  "hasRelativeAssetsUrls": false,
  "path": "../samples/grids/grid/binding-nested-data-1/src/index.css",
  "content": "/* shared styles are loaded from: */\r\n/* https://static.infragistics.com/xplatform/css/samples */\r\n",
  "isMain": true,
  "fileExtension": "css",
  "fileHeader": "css"
 }

Instead the content should be properly obtained from the samples' css files.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.