Skip to content

Commit

Permalink
v23.1.36 is released
Browse files Browse the repository at this point in the history
  • Loading branch information
pipeline committed Sep 15, 2023
1 parent 833a50a commit 80579fb
Show file tree
Hide file tree
Showing 2,066 changed files with 851 additions and 5,277 deletions.
1,213 changes: 1 addition & 1,212 deletions README.md

Large diffs are not rendered by default.

Expand Up @@ -18,6 +18,7 @@ export class BarcodeGeneratorComponent extends BarcodeGenerator {
public initRenderCalled: boolean = false;
private checkInjectedModules: boolean = true;
private statelessTemplateProps: string[] = null;
private templateProps: string[] = null;
private immediateRender: boolean = true;
public props: Readonly<{ children?: React.ReactNode | React.ReactNode[] }>
& Readonly<BarcodeGeneratorModel & DefaultHtmlAttributes>;
Expand Down
Expand Up @@ -18,6 +18,7 @@ export class DataMatrixGeneratorComponent extends DataMatrixGenerator {
public initRenderCalled: boolean = false;
private checkInjectedModules: boolean = true;
private statelessTemplateProps: string[] = null;
private templateProps: string[] = null;
private immediateRender: boolean = true;
public props: Readonly<{ children?: React.ReactNode | React.ReactNode[] }>
& Readonly<DataMatrixGeneratorModel & DefaultHtmlAttributes>;
Expand Down
Expand Up @@ -18,6 +18,7 @@ export class QRCodeGeneratorComponent extends QRCodeGenerator {
public initRenderCalled: boolean = false;
private checkInjectedModules: boolean = true;
private statelessTemplateProps: string[] = null;
private templateProps: string[] = null;
private immediateRender: boolean = true;
public props: Readonly<{ children?: React.ReactNode | React.ReactNode[] }>
& Readonly<QRCodeGeneratorModel & DefaultHtmlAttributes>;
Expand Down
@@ -0,0 +1,2 @@
@import 'ej2-base/styles/definition/material3-dark.scss';
@import 'ej2-barcode-generator/styles/barcode/material3-dark.scss';
2 changes: 2 additions & 0 deletions components/barcodegenerator/styles/barcode/material3.scss
@@ -0,0 +1,2 @@
@import 'ej2-base/styles/definition/material3.scss';
@import 'ej2-barcode-generator/styles/barcode/material3.scss';
2 changes: 2 additions & 0 deletions components/barcodegenerator/styles/material3-dark.scss
@@ -0,0 +1,2 @@

@import 'barcode/material3-dark.scss';
2 changes: 2 additions & 0 deletions components/barcodegenerator/styles/material3.scss
@@ -0,0 +1,2 @@

@import 'barcode/material3.scss';
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
9 changes: 8 additions & 1 deletion components/base/CHANGELOG.md
Expand Up @@ -2,14 +2,21 @@

## [Unreleased]

## 23.1.36 (2023-09-15)

### Common

#### Bug Fixes

- `#I479747` - The issue with "sample browser level codes are present in React stack blitz samples" has been resolved.

## 22.2.5 (2023-07-27)

### Common

#### Bug Fixes

- `#F181035` - The issue with "the Schedule component throwing compilation issues while using the timeScale property in the TypeScript sample" has been resolved.
- `#I479747` - The issue with "sample browser level codes are present in React stack blitz samples" has been resolved.

## 22.1.34 (2023-06-21)

Expand Down
2 changes: 1 addition & 1 deletion components/base/package.json
@@ -1,6 +1,6 @@
{
"name": "@syncfusion/ej2-react-base",
"version": "22.2.5",
"version": "23.1.36",
"description": "A common package of Essential JS 2 React base, methods and class definitions",
"author": "Syncfusion Inc.",
"license": "SEE LICENSE IN license",
Expand Down
183 changes: 183 additions & 0 deletions components/base/releasenotes/README.md
@@ -0,0 +1,183 @@
# Release Notes Guidelines

This section contains guidelines on naming files, sections and other document elements.

> **If there is no changes in product, you don't need to mention that in Release Notes.**
## Encoding Format

All Release Notes files should be saved in **Encoding in UTF-8 (Without BOM)** format. You can use Notepad++ to verify the encoding.

![Encoding.png](https://bitbucket.org/repo/j57Gz9/images/2199960455-Encoding.png)

## Release Notes Folder Hierarchy

* Platform [Folder]
* ----ReleaseNotes [Folder]
* --------v13.3.x.x [Folder]
* ------------Control1.md
* ------------Control2.md
* ------------Control3.md
* --------v13.4.x.x [Folder]
* ------------Control1.md
* ------------Control2.md
* ------------Control3.md

### How to write Release Notes?

* Each release markdown files should reside under corresponding version folder in their platform.
* Each product release notes should be created in separate file name.
* File name should be same as the product name.

> **NOTE**: Please do not add any Front Matter information in Release Notes files.
## Markdown File Structure

Each markdown file should have following items.

* Control Name
* Features
* Bug fixes
* Braking Changes
* Known Issues

> Do not add any front matter(triple dashed line) in this markdown.
### Control Name

Control Name should be with prefix `##`. This will be rendered as `H2` in html file.

#### Syntax

```
## <Control-Name>
```

#### Example

```
## ejAccrodion
```

### Features

* Each features should be written in unordered list.
* Feature header should have id in the following format `<control-name>-features`. All characters in **id should be written in lower case.**

#### Syntax

```
### Features
{:#<control-name>-features}
* \#1 - Feature Info
* \#2 - Feature Info
* \#3 - Feature Info
```

#### Example

```
### Features
{:#ejaccordion-features}
* \#140303 - Accordion provides option to add new items dynamically by using the `addItem` method
* \#140303 - Accordion provides option to add new items dynamically by using the `addItem` method
* \#140303, \#140304 - Accordion provides option to add new items dynamically by using the `addItem` method
```

> **NOTE:**
> * In markdown `#` used to represent headers.
> * By default it will be converted as HTML headers.
> * To display the `#` in html, please use escape sequences [See above example].
### Bug Fixes

* Each bug fix should be written in unordered list.
* Bug fixes header should have id in the following format `<control-name>-bug-fixes`. All characters in **id should be written in lower case.**

#### Syntax

```
### Bug fixes
{:#<control-name-in-lower-case>-bug-fixes}
* \#1 - Bug Fix
* \#2 - Bug Fix
* \#3 - Bug Fix
```

#### Example

```
### Bug Fixes
{:#ejaccordion-bug-fixes}
* \#140303 - Accordion provides option to add new items dynamically by using the `addItem` method
* \#140303 - Accordion provides option to add new items dynamically by using the `addItem` method
* \#140303, \#140304 - Accordion provides option to add new items dynamically by using the `addItem` method
```

> **NOTE:**
> * In markdown `#` used to represent headers.
> * By default it will be converted as HTML headers.
> * To display the `#` in html, please use escape sequences [See above example].
### Breaking Changes

* Each breaking changes should be written in unordered list.
* Breaking changes header should have id in the following format `<control-name>-breaking-changes`. All characters in **id should be written in lower case.**

```
### Breaking Changes
{:#<control-name>-breaking-changes}
* * Breaking Change 1
* * Breaking Change 2
* * Breaking Change 3
```

#### Example

```
### Breaking Changes
{:#ejaccordion-breaking-changes}
* Now, Circular series end angle will not be adjusted based on the start angle, so the output will be like semi-circle instead of full circle. In order to render the complete circular series with customized start angle, you have to add the start angle value to end angle property now. This break will occur only if you have specified startAngle already
```

> **NOTE:**
> * In markdown `#` used to represent headers.
> * By default it will be converted as HTML headers.
> * To display the `#` in html, please use escape sequences [See above example].
## Incidents and Forums in Release notes

We can represent the Incident ID with I and F for forums in release notes MD files

#### Example


```
## ChromelessWindow
### Bug Fixes
{:#chromelesswindow-bug-fixes}
* \#I336220 - When using `ShowDialog` on a `RibbonWindow`, a `NullReferenceException` will no longer occur.
* \#F166385 - The gap between the bottom of the window and the `TaskBar` is now properly maintained.
```

This is published in the page : https://help.syncfusion.com/wpf/release-notes/v19.3.0.43?type=all#chromelesswindow


## Commit

Same workflow for User Guide applicable to this repository. All the changes needs to be committed in `development` branch.

## Preview Changes

All the changes will be included with User Guide automation and published in Staging Documentation machine.

<http://115.249.201.211:9090>

0 comments on commit 80579fb

Please sign in to comment.