PhongPham
c65cc97a33
✨ MAJOR FEATURES: • Auto-zoom intelligence với smart bounds fitting • Enhanced 3D GPS markers với pulsing effects • Professional route display với 6-layer rendering • Status-based parking icons với availability indicators • Production-ready build optimizations 🗺️ AUTO-ZOOM FEATURES: • Smart bounds fitting cho GPS + selected parking • Adaptive padding (50px) cho visual balance • Max zoom control (level 16) để tránh quá gần • Dynamic centering khi không có selection 🎨 ENHANCED VISUALS: • 3D GPS marker với multi-layer pulse effects • Advanced parking icons với status colors • Selection highlighting với animation • Dimming system cho non-selected items 🛣️ ROUTE SYSTEM: • OpenRouteService API integration • Multi-layer route rendering (glow, shadow, main, animated) • Real-time distance & duration calculation • Visual route info trong popup 📱 PRODUCTION READY: • SSR safe với dynamic imports • Build errors resolved • Global deployment via Vercel • Optimized performance 🌍 DEPLOYMENT: • Vercel: https://whatever-ctk2auuxr-phong12hexdockworks-projects.vercel.app • Bundle size: 22.8 kB optimized • Global CDN distribution • HTTPS enabled 💾 VERSION CONTROL: • MapView-v2.0.tsx backup created • MAPVIEW_VERSIONS.md documentation • Full version history tracking
68 lines
1.5 KiB
Markdown
68 lines
1.5 KiB
Markdown
# jsx-a11y/heading-has-content
|
|
|
|
💼 This rule is enabled in the following configs: ☑️ `recommended`, 🔒 `strict`.
|
|
|
|
<!-- end auto-generated rule header -->
|
|
|
|
Enforce that heading elements (`h1`, `h2`, etc.) have content and that the content is accessible to screen readers. Accessible means that it is not hidden using the `aria-hidden` prop. Refer to the references to learn about why this is important.
|
|
|
|
## Rule options
|
|
|
|
This rule takes one optional object argument of type object:
|
|
|
|
```json
|
|
{
|
|
"rules": {
|
|
"jsx-a11y/heading-has-content": [ 2, {
|
|
"components": [ "MyHeading" ],
|
|
}],
|
|
}
|
|
}
|
|
```
|
|
|
|
For the `components` option, these strings determine which JSX elements (**always including** `<h1>` thru `<h6>`) should be checked for having content. This is a good use case when you have a wrapper component that simply renders an `h1` element (like in React):
|
|
|
|
|
|
```js
|
|
// Header.js
|
|
const Header = props => {
|
|
return (
|
|
<h1 {...props}>{ props.children }</h1>
|
|
);
|
|
}
|
|
|
|
...
|
|
|
|
// CreateAccount.js (for example)
|
|
...
|
|
return (
|
|
<Header>Create Account</Header>
|
|
);
|
|
```
|
|
|
|
#### Bad
|
|
```jsx
|
|
function Foo(props) {
|
|
return <label {...props} />
|
|
}
|
|
```
|
|
|
|
### Succeed
|
|
```jsx
|
|
<h1>Heading Content!</h1>
|
|
<h1><TextWrapper /><h1>
|
|
<h1 dangerouslySetInnerHTML={{ __html: 'foo' }} />
|
|
```
|
|
|
|
### Fail
|
|
```jsx
|
|
<h1 />
|
|
<h1><TextWrapper aria-hidden />
|
|
```
|
|
|
|
## Accessibility guidelines
|
|
- [WCAG 2.4.6](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html)
|
|
|
|
### Resources
|
|
- [axe-core, empty-heading](https://dequeuniversity.com/rules/axe/3.2/empty-heading)
|