-
Notifications
You must be signed in to change notification settings - Fork 3
Update the landing page link to spec #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
7cf103c
doc: massive web-site and documentation update
Artifizer fc5210b
docs: added GTS Kit VS Code plugin screenshots
Artifizer 936a726
Merge branch 'main' into docs-update
Artifizer e1c71db
docs: update examples
Artifizer faf1ce7
Merge branch 'main' into docs-update
Artifizer 7abbad5
chore: update third-party dependencies
Artifizer 7c08ff5
Merge branch 'main' into docs-update
Artifizer e42aebb
docs: update 'why GTS' section
Artifizer 4a07444
fix: use proper links to the specification
Artifizer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: GlobalTypeSystem/gts-web
Length of output: 1713
🏁 Script executed:
Repository: GlobalTypeSystem/gts-web
Length of output: 2820
🌐 Web query:
React 19 JSX class attribute className official documentation invalid DOM property warning💡 Result:
In React 19, you must continue to use
classNameinstead ofclasswhen defining CSS classes on standard DOM elements in JSX [1][2][3]. Usingclassremains invalid and will trigger an "Invalid DOM property" warning in the console [4][5][6]. The requirement exists for two primary reasons: 1. Reserved Keyword: In JavaScript,classis a reserved keyword used for class declarations [2][3]. Since JSX is an extension of JavaScript, usingclassas an attribute name would cause a syntax error during transpilation [3][7]. 2. Consistency and Tooling: React usesclassNameas the canonical property name for the DOMclassattribute [1][8]. Using a consistent naming convention allows React components to reliably manage and merge class names through props, avoiding conflicts that would arise if bothclassandclassNamewere supported interchangeably [8][7]. When React renders your components to the browser, it automatically maps theclassNameprop to the correctclassattribute in the generated HTML [2][3][8]. If you encounter this warning, you should update your code to replace all instances ofclasswithclassName[5][8]. Most modern development environments include linters (such aseslint-plugin-react) that automatically detect and flag this issue during development [3][8].Citations:
Replace
classwithclassNameon both<code>elements.React JSX uses
classNamefor CSS classes. The current props can trigger an invalid DOM-property warning and fail TypeScript validation.🤖 Prompt for AI Agents