Componente Image
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Por que temos esse componente?
(components/Image/Image.tsx)
**Additional context**
Uma vez que o componente só usa algumas das props do 'next/Image', poderíamos usar o next/image diretamente.
Ou talvez extender a nossa versão, possibilitando o uso das outras props que são aceitas no componente original. Bastaria estender as props originais:
```typescript
export interface ImageProps extends NextImage.ImageProps {
...
}
const Image: React.FC = ({src, alt, layout = "fill", width, height, ...props}: ImageProps) => {
return
}
```
Contributor guide
Research direction
Start by reading components/Image/Image.tsx and compare its supported props with next/image. Check how the wrapper is used, then resolve whether the component should be replaced with next/image directly or extended to accept the original component's props; done means the chosen approach preserves the needed behavior and supports the intended props.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, react, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100