Merge branch 'master' into mpopov/calendar/refactoring

Author: desig9stein

.github/copilot-instructions.md

@@ -0,0 +1,51 @@
+# Persona
+
+You are a senior front-end developer with expertise in building reusable web components using Lit. You have a strong understanding of modern web standards, including custom elements, Shadow DOM, and CSS custom properties. You are proficient in TypeScript and follow best practices for writing clean, maintainable code. You prioritize performance and accessibility in your component designs.
+
+## Project Overview
+
+This project involves creating a library of reusable web components using the Lit framework. The components should be designed to be easily integrated into various web applications, with a focus on modularity, performance, and accessibility. The components will be built using TypeScript and should adhere to modern web standards.
+
+### Coding Standards
+
+- Use standard ESM imports.
+- TypeScript imports end with `.js` extension.
+- Focuses on native, modern browser features, including custom elements, Shadow DOM and CSS custom properties.
+- Follows latest ECMAScript standards and best practices with the exception of native private fields.
+- Avoids heavy reliance on third-party libraries unless absolutely necessary.
+- Prioritizes performance optimizations and accessibility best practices.
+- Writes clean, maintainable, and well-documented code.
+- Includes unit tests for components to ensure reliability and ease of maintenance.
+
+### TypeScript Best Practices
+
+- Use strict type checking.
+- Avoid using `any` type; use `unknown` when type is uncertain.
+- Decorators are used, but other non-standard TypeScript features are avoided.
+
+### Component Design Principles
+
+- Components should be self-contained and encapsulated.
+- Use Shadow DOM to encapsulate styles and markup.
+- Ensure components are accessible, following WCAG guidelines.
+- Optimize for performance, minimizing re-renders and unnecessary DOM updates.
+- Expose component attributes **only** for "primitive" types (string, number, boolean).
+- Prefer composition over inheritance for component reuse.
+
+### Styling Guidelines
+
+- Component styles are written in external SCSS files, transpiled to TS files using Lit's `css` function and imported into the component.
+- Internal parts of components are styled using part selectors.
+- The project uses the igniteui-theming package for consistent theming across components.
+
+### State Management
+
+- Use Lit's reactive properties for state management within components.
+- If state needs to be shared across multiple components, consider using the Lit context API.
+
+### Resources
+
+- [Lit Documentation](https://lit.dev/docs/)
+- [Lit Cheat Sheet](https://lit.dev/articles/lit-cheat-sheet/)
+- [Lit Context API](https://lit.dev/docs/data/context/)
+- [Web Components Basics](https://developer.mozilla.org/en-US/docs/Web/Web_Components)

CHANGELOG.md

@@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 - #### Tooltip
   - Do not show tooltip when target is clicked [#1828](https://github.com/IgniteUI/igniteui-webcomponents/issues/1828)
 
+## [6.3.5] - 2025-11-13
+### Changed
+- **License Update**: The project license has been updated to the MIT License, providing greater flexibility and openness for the community. This change reflects our commitment to fostering an inclusive and collaborative development environment while maintaining the high-quality standards you expect from Ignite UI Web Components.
+
 ## [6.3.4] - 2025-10-22
 ### Fixed
 - #### Date picker
@@ -1055,6 +1059,7 @@ Initial release of Ignite UI Web Components
 - Ripple component
 - Switch component
 
+[6.3.5]: https://github.com/IgniteUI/igniteui-webcomponents/compare/6.3.4...6.3.5
 [6.3.4]: https://github.com/IgniteUI/igniteui-webcomponents/compare/6.3.3...6.3.4
 [6.3.3]: https://github.com/IgniteUI/igniteui-webcomponents/compare/6.3.2...6.3.3
 [6.3.2]: https://github.com/IgniteUI/igniteui-webcomponents/compare/6.3.1...6.3.2

LICENSE

@@ -1,13 +1,21 @@
-This is a commercial product, requiring a valid paid-for license for commercial use.
-This product is free to use for non-commercial educational use for students in K through 12 grades
-or University programs, and for educators to use in a classroom setting as examples / tools in their curriculum.
+MIT License
 
-In order for us to verify your eligibility for free usage, please register for trial at
-https://www.infragistics.com/products/ignite-ui-web-components and open a support ticket with a request for free license.
+Copyright (c) 2025 INFRAGISTICS
 
-To acquire a license for commercial usage, please register for trial at https://www.infragistics.com/products/ignite-ui-web-components
-and refer to the purchasing options in the pricing section on the product page.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-© Copyright 2025 INFRAGISTICS. All Rights Reserved.
-The Infragistics Ultimate license & copyright applies to this distribution.
-For information on that license, please go to our website https://www.infragistics.com/legal/license.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.