You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat:Improvised component and added relevant templates (#11) (#12)
* Updated test files, storybook, readme and some code refactoring (#11)
* Renamed few functions and variables
* Updated storybook readme and test files
* Updated the codesandbox link and email
* Formatted the files and readme changes
* Added pull request template and style guidelines
* Added version and prettier config in package.json
* Fixed bug in the initial width calculation
* fix: package version change
We can also control the display of the legend consisting of the details regarding the colour distribution using the props 'showLegend' and 'legendPosition' as follows.
95
-
96
-
```jsx
97
-
<DotMatrix
98
-
dataPoints={dataPointsArray}
99
-
showLegend={true}
100
-
legendPosition="top"
101
-
/>
102
-
```
103
79
## Props
104
80
105
-
106
-
107
81
Props that can be passed to the component are listed below:
108
82
109
83
<table>
@@ -130,11 +104,11 @@ Props that can be passed to the component are listed below:
## SCSS Style Guidelines for @keyvaluesystems/react-dot-matrix-chart
2
+
3
+
**Introduction**
4
+
5
+
As an open-source project utilizing SCSS, @keyvaluesystems/react-dot-matrix-chart strives to maintain a consistent and well-structured codebase. These SCSS style guidelines serve as a reference for contributors, ensuring that their SCSS code adheres to established conventions and best practices.
6
+
7
+
**SCSS Coding Conventions**
8
+
9
+
- Organize SCSS files into a logical structure.
10
+
- Use meaningful and descriptive names for variables, mixins, and classes.
11
+
- Use SCSS nesting judiciously to organize complex styles.
12
+
- Include comments to explain non-obvious logic and complex styles.
13
+
- Utilize SCSS variables to define reusable values.
14
+
- Employ a SCSS linting tool.
15
+
- Should support devices with all resolutions.
16
+
- Follow CamelCase conventions for class names that concisely convey their purpose, enhancing code organization and readability.
17
+
- Adhere to the practice of reusing style classes to improve code organization and maintainability.
18
+
19
+
**Documentation Practices**
20
+
21
+
- Provide clear documentation for exported mixins and variables.
22
+
- Include a README file within the SCSS directory if necessary.
0 commit comments