jeremypele

import { AppiumDriver, createDriver, SearchOptions } from 'nativescript-dev-appium'
import { runType } from 'nativescript-dev-appium/lib/parser'
import { Direction } from 'nativescript-dev-appium/lib/direction'
import { assert } from 'chai'

const isAndroid: string = runType.includes('android')

describe('E2E Specs', () => {

  let driver: AppiumDriver

manoldonev

ROOT FRAME SCENARIOS:
1. Show modal dialog with frame
	1.1. Navigate to modal second page within modal dialog
		1.1.1. Go back
	1.2. Show nested modal dialog
		1.2.1. Close nested modal dialog
	1.3. Show nested modal dialog with frame
		1.3.1. Close nested modal dialog
	1.4. Close modal dialog
2. Show modal dialog

hshristov

One of the main goals of tns-core-modules@4.0 is to enable more flexible composition of UI. Let's start with some history. Before 4.0 we create Frame control for you (check application.ios.ts and frame.android.ts). Frame control allows you to do navigation forward or backward. While this is convenient it introduce other issues that can't be workaround easliy. For example if you want to have TabView in all pages you have to include it in the xml and set its selectedIndex so that once you navigate to different page a correct TabViewItem is selected. This leads to several problems:

• parse more xml
• increase memory usage
• increase loading time

Same issues apply if you want to have SideDrawer control as a root component.

So in order to resolve these starting with 4.0 applicat

sis0k0

#!/bin/bash
set -e

# release defaults to patch (last number in semver)
RELEASE="patch" && [ -n "$1" ] && RELEASE=$1

# cut the release
VERSION=$(npm --no-git-tag-version version $RELEASE | sed 's/v//')
git add package.json
git commit -m "release: cut the $VERSION release"