@umituz/react-native-onboarding 1.0.4 → 1.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@umituz/react-native-onboarding",
3
- "version": "1.0.4",
3
+ "version": "1.0.6",
4
4
  "description": "Generic onboarding flow for React Native apps with gradient backgrounds, animations, and customizable slides. SOLID, DRY, KISS principles applied.",
5
5
  "main": "./src/index.ts",
6
6
  "types": "./src/index.ts",
package/src/index.ts CHANGED
@@ -30,9 +30,7 @@
30
30
  // DOMAIN LAYER - Entities and Interfaces
31
31
  // =============================================================================
32
32
 
33
- // Export type with a different name to avoid conflict with component
34
- export type { OnboardingSlide as OnboardingSlideType } from "./domain/entities/OnboardingSlide";
35
- // Re-export as OnboardingSlide for backward compatibility (after component export)
33
+ export type { OnboardingSlide } from "./domain/entities/OnboardingSlide";
36
34
  export type { OnboardingOptions } from "./domain/entities/OnboardingOptions";
37
35
 
38
36
  // =============================================================================
@@ -57,18 +55,10 @@ export { OnboardingHeader, type OnboardingHeaderProps } from "./presentation/com
57
55
  export { OnboardingFooter, type OnboardingFooterProps } from "./presentation/components/OnboardingFooter";
58
56
 
59
57
  // Export OnboardingSlide component
60
- // Note: TypeScript doesn't allow exporting both a type and a value with the same name in the same scope
61
- // So we export the component, and the type is exported above as OnboardingSlideType
58
+ // Note: TypeScript doesn't allow exporting both a type and a value with the same name
59
+ // The type is exported above as OnboardingSlide
60
+ // The component is exported here with a different name to avoid conflict
62
61
  import { OnboardingSlide as OnboardingSlideComponent } from "./presentation/components/OnboardingSlide";
63
62
  export { OnboardingSlideComponent };
64
63
  export type { OnboardingSlideProps } from "./presentation/components/OnboardingSlide";
65
64
 
66
- // Export component as OnboardingSlide for backward compatibility
67
- // Users can import type as: import type { OnboardingSlideType } from '@umituz/react-native-onboarding'
68
- // And component as: import { OnboardingSlide } from '@umituz/react-native-onboarding'
69
- export { OnboardingSlideComponent as OnboardingSlide };
70
-
71
- // Re-export type as OnboardingSlide for backward compatibility (after component export)
72
- // This works because TypeScript allows type and value with same name in different declarations
73
- export type { OnboardingSlideType as OnboardingSlide };
74
-
@@ -13,7 +13,7 @@ import type { OnboardingOptions } from "../../domain/entities/OnboardingOptions"
13
13
  import { useOnboardingNavigation } from "../../infrastructure/hooks/useOnboardingNavigation";
14
14
  import { useOnboardingStore } from "../../infrastructure/storage/OnboardingStore";
15
15
  import { OnboardingHeader } from "../components/OnboardingHeader";
16
- import { OnboardingSlide } from "../components/OnboardingSlide";
16
+ import { OnboardingSlide as OnboardingSlideComponent } from "../components/OnboardingSlide";
17
17
  import { OnboardingFooter } from "../components/OnboardingFooter";
18
18
 
19
19
  export interface OnboardingScreenProps extends OnboardingOptions {
@@ -133,7 +133,7 @@ export const OnboardingScreen: React.FC<OnboardingScreenProps> = ({
133
133
  {renderSlide ? (
134
134
  renderSlide(currentSlide)
135
135
  ) : (
136
- <OnboardingSlide slide={currentSlide} />
136
+ <OnboardingSlideComponent slide={currentSlide} />
137
137
  )}
138
138
  {renderFooter ? (
139
139
  renderFooter({