react-native-calendar-resource 1.0.0 → 1.0.1

package/README.md

@@ -30,7 +30,7 @@ yarn add react-native-calendar-resource
 Ensure you have the required peer dependencies:
 
 ```bash
-npm install react react-native date-fns
+npm install  date-fns
 ```
 
 ---
@@ -288,7 +288,6 @@ interface BookingData {
 - Expo
 - TypeScript
 - date-fns
-- NativeWind (optional, for default styling)
 
 ---
 
@@ -304,100 +303,4 @@ Headers are disabled at the stack level and selectively enabled per screen to ma
 
 ---
 
-### Calendar Component
-
-The booking calendar was implemented from scratch instead of relying on third-party libraries.
-
-Reasons for this decision:
-
-1. No third-party library was found that met the requirements of the project.
-2. Pixel-perfect alignment with the design
-3. Full control over a resource-based grid (events × time)
-4. Optimized performance for the specific use case
-5. Reduced dependency and bundle size overhead
-
-#### Calendar Architecture
-
-```
-Calendar/
-├── Calendar.tsx
-├── CalendarHeader.tsx
-├── TimeColumn.tsx
-├── ResourceHeaders.tsx
-├── GridBody.tsx
-├── EventsLayer.tsx
-└── UnavailableLayer.tsx
-```
-
-#### Key Features
-
-- Synchronized horizontal and vertical scrolling
-- Resource-based layout for multiple events
-- Three slot states: available, booked, unavailable
-- Configurable time range, slot height, and column width
-- Cross-platform behavior parity (iOS & Android)
-
----
-
-### Styling Approach
-
-Styling is handled using NativeWind (TailwindCSS for React Native):
-
-- Semantic color tokens (background, card, accent, muted)
-- Consistent spacing and typography via utility classes
-- Centralized theme configuration
-- Custom fonts (Asap, Bebas Neue) loaded via `expo-font`
-- A mix of @expo/vector-icons and SVG icon components was used. SVGs were introduced for icons where an exact visual match was not available in the Expo icon set.
-
----
-
-### Date & Time Handling
-
-All date and time operations use date-fns for:
-
-- Clear and readable date manipulation
-- Tree-shakeable imports
-- Safer alternatives to native Date APIs
-
----
-
-## Tech Stack
-
-- Expo SDK 54
-- TypeScript
-- Expo Router + React Navigation Stack
-- NativeWind (TailwindCSS)
-- date-fns
-- react-native-leaflet-view (Leaflet maps via WebView)
-- expo-linear-gradient
-- react-native-reanimated
-
----
-
-## Implemented Features
-
-- Venue details screen with image carousel
-- Rating badges and amenity tags
-- Coach cards with detail navigation
-- Custom calendar grid
-- Date shortcuts (Today / Tomorrow)
-- Visual distinction between slot states
-- Location card with map preview
-- Persistent tab bar navigation
-- Nested stack navigation within Explore
-- Cross-platform support (iOS & Android)
-
----
-
-## Additional Notes
-
-- The Explore tab was used to display event details since no design was provided for the Home screen.
-  In a real-world application, the Explore tab would typically be used to search for or browse events, then navigate to the event details screen.
-- Non-Explore tabs are intentionally minimal as they are outside the task scope
-- Leaflet (via `react-native-leaflet-view`) was used for maps instead of `react-native-maps` or other Google Maps-based libraries, as those require a Google Cloud API key and billing subscription
-- Mock data is used throughout the app
-- Safe area insets are handled for iOS notch and home indicator
-
----
-
 **Author:** Abdelrahman Sobhy

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-calendar-resource",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "A fully customizable, type-safe resource-based calendar component for React Native",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",