Merge pull request #208 from a1mery/ChartCard-FilesByContentType-1.21.1-upgrade

Upgrade ChartCard-FilesByContentType to SPFx 1.21.1

Author: anoopt

samples/ChartCard-FilesByContentType/.eslintrc.js

@@ -1,4 +1,3 @@
-require('@rushstack/eslint-config/patch/modern-module-resolution');
 module.exports = {
   extends: ['@microsoft/eslint-config-spfx/lib/profiles/default'],
   parserOptions: { tsconfigRootDir: __dirname },
@@ -20,39 +19,6 @@ module.exports = {
         '@rushstack/security/no-unsafe-regexp': 1,
         // STANDARDIZED BY:   @typescript-eslint\eslint-plugin\dist\configs\recommended.json
         '@typescript-eslint/adjacent-overload-signatures': 1,
-        // STANDARDIZED BY:   @typescript-eslint\eslint-plugin\dist\configs\recommended.json
-        //
-        // CONFIGURATION:     By default, these are banned: String, Boolean, Number, Object, Symbol
-        '@typescript-eslint/ban-types': [
-          1,
-          {
-            'extendDefaults': false,
-            'types': {
-              'String': {
-                'message': 'Use \'string\' instead',
-                'fixWith': 'string'
-              },
-              'Boolean': {
-                'message': 'Use \'boolean\' instead',
-                'fixWith': 'boolean'
-              },
-              'Number': {
-                'message': 'Use \'number\' instead',
-                'fixWith': 'number'
-              },
-              'Object': {
-                'message': 'Use \'object\' instead, or else define a proper TypeScript type:'
-              },
-              'Symbol': {
-                'message': 'Use \'symbol\' instead',
-                'fixWith': 'symbol'
-              },
-              'Function': {
-                'message': 'The \'Function\' type accepts any function-like value.\nIt provides no type safety when calling the function, which can be a common source of bugs.\nIt also accepts things like class declarations, which will throw at runtime as they will not be called with \'new\'.\nIf you are expecting the function to accept certain arguments, you should explicitly define the function shape.'
-              }
-            }
-          }
-        ],
         // RATIONALE:         Code is more readable when the type of every variable is immediately obvious.
         //                    Even if the compiler may be able to infer a type, this inference will be unavailable
         //                    to a person who is reviewing a GitHub diff.  This rule makes writing code harder,
@@ -79,7 +45,7 @@ module.exports = {
         //                    This rule should be suppressed only in very special cases such as JSON.stringify()
         //                    where the type really can be anything.  Even if the type is flexible, another type
         //                    may be more appropriate such as "unknown", "{}", or "Record<k,V>".
-        '@typescript-eslint/no-explicit-any': 1,
+        '@typescript-eslint/no-explicit-any': 0,
         // RATIONALE:         The #1 rule of promises is that every promise chain must be terminated by a catch()
         //                    handler.  Thus wherever a Promise arises, the code must either append a catch handler,
         //                    or else return the object to a caller (who assumes this responsibility).  Unterminated
@@ -298,7 +264,7 @@ module.exports = {
         'no-with': 2,
         // RATIONALE:         Makes logic easier to understand, since constants always have a known value
         // @typescript-eslint\eslint-plugin\dist\configs\eslint-recommended.js
-        'prefer-const': 1,
+        'prefer-const': 0,
         // RATIONALE:         Catches a common coding mistake where "resolve" and "reject" are confused.
         'promise/param-names': 2,
         // RATIONALE:         Catches code that is likely to be incorrect

samples/ChartCard-FilesByContentType/.yo-rc.json

@@ -7,7 +7,7 @@
       "@microsoft/microsoft-graph-client": "3.0.2",
       "@microsoft/teams-js": "2.24.0"
     },
-    "version": "1.20.0-beta.0",
+    "version": "1.21.1",
     "libraryName": "chart-card-files-by-content-type",
     "libraryId": "1ac895fb-8ac0-44ce-9b5a-61b9dba15ff4",
     "environment": "spo",

samples/ChartCard-FilesByContentType/README.md

@@ -15,7 +15,7 @@ Medium view:
 
 ## Used SharePoint Framework Version
 
-![version](https://img.shields.io/badge/version-1.20.0--beta.0-yellow.svg)
+![version](https://img.shields.io/badge/version-1.21.1-yellow.svg)
 
 ## Applies to
 
@@ -38,6 +38,7 @@ Medium view:
 | Version | Date             | Comments        |
 | ------- | ---------------- | --------------- |
 | 1.0     | September 08, 2024 | Initial release |
+| 1.1     | October 29, 2025 | Upgrade to SPFx 1.21.1 |
 
 ## Disclaimer
 

samples/ChartCard-FilesByContentType/config/package-solution.json

@@ -3,7 +3,7 @@
   "solution": {
     "name": "chart-card-files-by-content-type-client-side-solution",
     "id": "1ac895fb-8ac0-44ce-9b5a-61b9dba15ff4",
-    "version": "1.0.0.0",
+    "version": "1.1.0.0",
     "includeClientSideAssets": true,
     "skipFeatureDeployment": true,
     "isDomainIsolated": false,