🔧 (react-nonav) rename gondola to nonav

Author: tpucci

CHANGELOG.md

@@ -3,9 +3,9 @@
 <p align="center">React Native declarative and reactive navigation.</p>
 
 <p align="center">
-<a href="https://travis-ci.com/tpucci/react-gondola"><img src="https://travis-ci.com/tpucci/react-gondola.svg?branch=master" alt="Build Status"/></a>
-<a href="https://coveralls.io/github/tpucci/react-gondola?branch=master"><img src="https://coveralls.io/repos/github/tpucci/react-gondola/badge.svg?branch=master" alt="Coverage Status"/></a>
-<a href="https://www.npmjs.com/package/react-gondola"><img src="https://img.shields.io/npm/dw/react-gondola.svg" alt="NPM Downloads"/></a>
+<a href="https://travis-ci.com/tpucci/react-nonav"><img src="https://travis-ci.com/tpucci/react-nonav.svg?branch=master" alt="Build Status"/></a>
+<a href="https://coveralls.io/github/tpucci/react-nonav?branch=master"><img src="https://coveralls.io/repos/github/tpucci/react-nonav/badge.svg?branch=master" alt="Coverage Status"/></a>
+<a href="https://www.npmjs.com/package/react-nonav"><img src="https://img.shields.io/npm/dw/react-nonav.svg" alt="NPM Downloads"/></a>
 <a href="http://commitizen.github.io/cz-cli/"><img src="https://img.shields.io/badge/commitizen-friendly-brightgreen.svg" alt="Commitizen friendly"/></a>
 <a href="https://github.com/semantic-release/semantic-release"><img src="https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg" alt="semantic-release"/></a>
 </p>
@@ -14,9 +14,9 @@
 
 ## Philosophy
 
-This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-gondola`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
+This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-nonav`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
 
-**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-gondola` takes care of the rest.
+**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
 
 ## 👍 TLDR; Use this package if:
 
@@ -27,11 +27,11 @@ This repo focuses on grouping screens by business conversion tunnels called **ca
 ## 👎 Do not use this repo if:
 
 - you want to navigate imperatively.
-- you need to use Native navigation (react-gondola's navigation is powered by JS code only).
+- you need to use Native navigation (react-nonav's navigation is powered by JS code only).
 
 ## Docs
 
-The docs are here: https://react-gondola.netlify.com/
+The docs are here: https://react-nonav.netlify.com/
 Powered by the incredible [docz](https://www.docz.site/).
 
 ## Contribute

README.md

@@ -7,7 +7,7 @@ route: /getting-started
 
 ## Installation
 
-React-gondola needs the following dependencies; if you do not have those installed, you need to install them with the correspondig command:
+React-nonav needs the following dependencies; if you do not have those installed, you need to install them with the correspondig command:
 
 |     Dependencie name      |     Yarn Installation command      |    NPM Installation command     |
 | :-----------------------: | :--------------------------------: | :-----------------------------: |
@@ -16,13 +16,13 @@ React-gondola needs the following dependencies; if you do not have those install
 
 Then, follow any post-installation instruction of `react-native-reanimated`. See [`react-native-reanimated` Installation Instructions](https://github.com/kmagiera/react-native-reanimated#installation).
 
-Then, install React-Gondola with:
+Then, install React-Nonav with:
 
-`yarn add react-gondola`
+`yarn add react-nonav`
 
 or
 
-`npm i react-gondola`
+`npm i react-nonav`
 
 ## Basic Usage
 
@@ -32,7 +32,7 @@ In order to create a canal, use the `Canal` and `Screen` components. Your screen
 
 ```ts
 import React from 'react';
-import { Canal, Screen } from 'react-gondola';
+import { Canal, Screen } from 'react-nonav';
 import { FirstName } from './FirstName';
 import { LastName } from './LastName';
 
@@ -52,7 +52,7 @@ If you want to add full screen page, pass the `isFullScreen` flag prop to your `
 
 ```ts
 import React from 'react';
-import { Canal, Screen } from 'react-gondola';
+import { Canal, Screen } from 'react-nonav';
 import { FirstName } from './FirstName';
 import { LastName } from './LastName';
 
@@ -69,7 +69,7 @@ In order to render the full screen page, add the `FullScreenPortal` at the top l
 ```ts
 import React, { Component } from 'react';
 import { MyCanal } from './canals/MyCanal';
-import { FullScreenPortal } from 'react-gondola';
+import { FullScreenPortal } from 'react-nonav';
 
 export default class App extends Component {
   render() {
@@ -88,7 +88,7 @@ Back events are also managed in a declarative way. Use the `onBack` callback pro
 
 ```ts
 import React from 'react';
-import { Canal, Screen } from 'react-gondola';
+import { Canal, Screen } from 'react-nonav';
 import { FirstName } from './FirstName';
 import { LastName } from './LastName';
 
@@ -123,4 +123,4 @@ import { Warning } from 'components/Warning';
   - Deepest visible screen.
 </Info>
 
-You are ready to use React-Gondola 🎸.
+You are ready to use React-Nonav 🎸.

docs/GettingStarted.mdx

@@ -5,7 +5,7 @@ route: /roadmap
 
 # Roadmap
 
-If there is a real interest on `react-gondola` and its phylosophy, I might add support for the following features:
+If there is a real interest on `react-nonav` and its phylosophy, I might add support for the following features:
 
 import { StrikeThrough } from "./components/StrikeThrough";
 
@@ -18,11 +18,11 @@ Tweet me some encouragements 😁 and star the repo !
 import GitHubButton from "react-github-btn";
 
 <GitHubButton
-  href="https://github.com/tpucci/react-gondola"
+  href="https://github.com/tpucci/react-nonav"
   data-icon="octicon-star"
   data-size="large"
   data-show-count="true"
-  aria-label="Star tpucci/react-gondola on GitHub"
+  aria-label="Star tpucci/react-nonav on GitHub"
 >
   Star
 </GitHubButton>

docs/Roadmap.mdx

@@ -9,9 +9,9 @@ React Native declarative and reactive navigation.
 
 ## Philosophy
 
-This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-gondola`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
+This repo focuses on grouping screens by business conversion tunnels called **canals**. Why did I call it `react-nonav`? Just because I though of this package when I was visiting Venice... and I kind of hope that using this package will feel like navigating in Venice 📸
 
-**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-gondola` takes care of the rest.
+**When you use React Gondola**, you define several screens and you have the possibility to control their visibility with YOUR state machine. You define the rules of WHEN some screens should appear; `react-nonav` takes care of the rest.
 
 ## When to use this package
 
@@ -24,7 +24,7 @@ This repo focuses on grouping screens by business conversion tunnels called **ca
 ### 👎 Do not use this repo if:
 
 - you want to navigate imperatively.
-- you need to use Native navigation (react-gondola's navigation is powered by JS code only).
+- you need to use Native navigation (react-nonav's navigation is powered by JS code only).
 
 ## Compare
 

docs/Welcome.mdx

@@ -11,7 +11,7 @@ route: /guides/back
 In order to go back, you need to code two steps.
 
 1. Add a `onBack` callback on the `Screen` you are going back from. Make sure this callback affects the visibility (prop `visible`) of the screen you are going back from.
-2. Call `Navigation.instance.back()` (`import { Navigation } from 'react-gondola'`).
+2. Call `Navigation.instance.back()` (`import { Navigation } from 'react-nonav'`).
 
 You're set 🎸.
 

docs/guides/Back.mdx

@@ -11,14 +11,14 @@ Yes it can.
 ## Good use of both of us 👍
 
 1. The user is free to navigate on some top level pages (use `react-navigation`).
-2. The user is forced to move forward/backward when he completes come steps in low level tunnels (use `react-gondola`).
+2. The user is forced to move forward/backward when he completes come steps in low level tunnels (use `react-nonav`).
 
 This means that at a certain point in your navigation, you need to control the visibility of your page. That great power comes with great responsability.
 ✅ Test your state machine !
 
 ## How well it works ?
 
-**Disclaimer:** interoperability has not been entirely tested. If you encounter any issue, feel free to open an issue on the `react-gondola` repo.
+**Disclaimer:** interoperability has not been entirely tested. If you encounter any issue, feel free to open an issue on the `react-nonav` repo.
 
 ## Steps
 

docs/guides/ReactNavigationInteroperability.mdx

@@ -12,7 +12,7 @@ In order to use transitions between two screens, simply add the `Transitioner` k
 
 ```ts
 import React from 'react';
-import { Canal, Screen, transitions } from 'react-gondola';
+import { Canal, Screen, transitions } from 'react-nonav';
 import { FirstName } from './FirstName';
 import { LastName } from './LastName';
 
@@ -41,7 +41,7 @@ You can create your own transitioner if the one availables does not fit your nee
 
 1. Your transitioner need to extend `TransitionComponent`.
 2. Your transitioner will receive a `directionForward` prop. If true, your transitioner need to play the transition forward. Else, it need to play the transition backward.
-3. (Optionnal but recommended) If you use jest, you can test your component using `describeTransitioner` from `react-gondola/transitions/describeTransitioner`
+3. (Optionnal but recommended) If you use jest, you can test your component using `describeTransitioner` from `react-nonav/transitions/describeTransitioner`
 
 ⚠️ If you use jest and want to test you Transitioner wihch uses `react-native-reanimated`, make sure you correctly mocked `react-native-reanimated`.
 

docs/guides/Transitions.mdx

@@ -17,7 +17,7 @@ module.exports = {
     config.resolve.alias = Object.assign({}, config.resolve.alias, {
       components: path.resolve(__dirname, 'docs/components/'),
       'react-native$': 'react-native-web',
-      'react-gondola$': path.resolve(__dirname, 'src/index.ts'), // eslint-disable-line
+      'react-nonav$': path.resolve(__dirname, 'src/index.ts'), // eslint-disable-line
       'react-native-reanimated$': path.resolve(__dirname, 'docs/mocks/react-native-reanimated'), // eslint-disable-line
     });
     return config;

doczrc.js

@@ -6,8 +6,8 @@ module.exports = {
   rootDir: '..',
   testPathIgnorePatterns: ['/node_modules/', '<rootDir>/src/'],
   moduleNameMapper: {
-    '^react-gondola$': '<rootDir>/src/',
-    '^react-gondola/transitions$': '<rootDir>/src/transitions',
+    '^react-nonav$': '<rootDir>/src/',
+    '^react-nonav/transitions$': '<rootDir>/src/transitions',
   },
   setupFilesAfterEnv: ['<rootDir>/jest/setup.js'],
 };