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
kalisjoshua opened this issue
Dec 26, 2024
· 2 comments
Labels
choreOther changes that don't modify source or test filesdeveloperIssues or tickets that are currently in developers wheelhousequestionA question regarding the code or functionalitysetupRepo setup and architecture
There is a way to configure projects to assume React is in scope for .tsx files which will remove the requirement to import React explicitly. Adding this config would remove the need to explictly import React and disable the biome linting rule "lint/correctness/noUnusedImports".
The text was updated successfully, but these errors were encountered:
kalisjoshua
added
chore
Other changes that don't modify source or test files
developer
Issues or tickets that are currently in developers wheelhouse
question
A question regarding the code or functionality
setup
Repo setup and architecture
labels
Dec 26, 2024
@kalisjoshua in any case we would, at a bare minimum, need to define react as a peer dependency which will install it anyways. Note we don't import from react explicitly unless it is for a particular hook or type e.g.
import { useState } from 'react';
We do not do a glob or default import of
import * as React from 'react';
// or
import React from 'react';
choreOther changes that don't modify source or test filesdeveloperIssues or tickets that are currently in developers wheelhousequestionA question regarding the code or functionalitysetupRepo setup and architecture
There is a way to configure projects to assume
React
is in scope for.tsx
files which will remove the requirement to import React explicitly. Adding this config would remove the need to explictly import React and disable the biome linting rule "lint/correctness/noUnusedImports".The text was updated successfully, but these errors were encountered: