react-native-windows/.gitignore

193 строки
2.2 KiB
Plaintext
Исходник Обычный вид История

#Node
# Logs
logs
*.log
npm-debug.log*
# Runtime data
pids
*.pid
*.seed
# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov
# Coverage directory used by tools like istanbul
coverage
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt
# node-waf configuration
.lock-wscript
# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release
# Dependency directory
node_modules
# Optional npm cache directory
.npm
# Optional REPL history
.node_repl_history
# No NPM config to pass CFS compliance
.npmrc
# We use yarn, not npm
package-lock.json
#React Native
*AppPackages*
*BundleArtifacts*
*ReactAssets*
#OS junk files
[Tt]humbs.db
*.DS_Store
#Visual Studio files
*.[Oo]bj
*.user
*.aps
*.pch
*.vspscc
*.vssscc
*_i.c
*_p.c
*.ncb
*.suo
*.tlb
*.tlh
*.tlog
*.bak
*.[Cc]ache
*.ilk
*.log
*.lib
*.sbr
*.sdf
*.opensdf
*.opendb
*.unsuccessfulbuild
*.lastbuildstate
ipch/
[Oo]bj/
[Bb]in
[Dd]ebug/
[Rr]elease/
*.tlog/
Ankh.NoLoad
Re-enable Shared tests for the Universal build (#840) * The NMock3 library is not compatiable with Universal Windows Projects... Any TestFixtures that utilize the NMock3 library need to be isolated in the .NET test project(s)... Moved NMock3 related tests from ReactiveNative.Shared.Tests to ReactNative46.Tests. The majority of tests in JavaScriptModuleBaseTests.cs utilized NMock so the entire file was moved from the ReactiveNative.Shared.Tests to the ReactNative.Net46.Tests projects. A handful of tests in JavaScriptModuleRegistryTests.cs utilized NMock. A specialized class inheriting from JavaScriptModuleRegistryTests was added to the ReactNative.Net46.Tests project. The specialized class "JavaScriptModuleRegistryNMockTests" contains only the NMock dependent tests and the base class contains all tests that can be shared. All references to NMock have been removed from the test code in the ReactNative.Shared.Tests projects... A reference to the ReactNative.Shared.Tests has been added to the ReactNative.Tests project. Additionally, the NUnit v3.41 nuGet package and the NUnit3TestAdapter v 3.5 nuGet package were added to the ReactNative.Tests project. The NUnit3TestAdapter v 3.41 nuGet package could not be loaded in the ReactNative.Tests project so v3.5 (the latest) was used. This creates a version mismatch with the NUnit package and the nuGet packages used in the ReactNative.Net46.Tests project... * The NMock3 library is not compatiable with Universal Windows Projects... Any TestFixtures that utilize the NMock3 library need to be isolated in the .NET test project(s)... Moved NMock3 related tests from ReactiveNative.Shared.Tests to ReactNative46.Tests. The majority of tests in JavaScriptModuleBaseTests.cs utilized NMock so the entire file was moved from the ReactiveNative.Shared.Tests to the ReactNative.Net46.Tests projects. A handful of tests in JavaScriptModuleRegistryTests.cs utilized NMock. A specialized class inheriting from JavaScriptModuleRegistryTests was added to the ReactNative.Net46.Tests project. The specialized class "JavaScriptModuleRegistryNMockTests" contains only the NMock dependent tests and the base class contains all tests that can be shared. All references to NMock have been removed from the test code in the ReactNative.Shared.Tests projects... A reference to the ReactNative.Shared.Tests has been added to the ReactNative.Tests project. Additionally, the NUnit v3.41 nuGet package and the NUnit3TestAdapter v 3.5 nuGet package were added to the ReactNative.Tests project. The NUnit3TestAdapter v 3.41 nuGet package could not be loaded in the ReactNative.Tests project so v3.5 (the latest) was used. This creates a version mismatch with the NUnit package and the nuGet packages used in the ReactNative.Net46.Tests project... * Removing "MockJavaScriptExecutor.cs" from ReactNative.Tests because it is already included in ReactNative.Shared.Tests * Renaming "JavaScriptModuleRegistryMockTests.cs" to "JavaScriptModuleRegistryNMockTests.cs" to match the class name... * Renaming JavaScriptModuleRegistryMockTests.cs to match the included class name... * Upgrade NUnit version in ReactNative.Tests project * Upgrade NUnit nuget references in ReactNative.Net46.Tests project to also be NUnit 3.5.0. NUnit upgraded to 3.5.0 NUnit3TestRunner upgraded to 3.5.1 * Syncing with upstream * Removing UpgradeLog.htm; adding UpgradeLog.htm to .gitignore * Adding appveyor.yml * * ReactNative.Shared.Tests: Renamed JavascriptModuleRegistryTests.cs and the containing class from JavascriptModuleRegistryTests to JavascriptModuleRegistrySharedTests. * ReactNative.Net46.Tests: Renamed JavascriptModuleRegistryNMockTests.cs and the containing class from JavascriptModuleRegistryNMockTests to JavascriptModuleRegistryTests. Changed the base class to JavascriptModuleRegistrySharedTests. * ReactNative.Tests: Added JavascriptModuleRegistryTests.cs to project that uses Univesal-specific mocking in place of NMock. Inherited containing class from JavascriptModuleRegistrySharedTests. * Adding new and renamed files * Restoring the 0.27-stable branch implementations of some universal specific tests in JavaScriptModuleRegistryTests * Removing npm install -g react-native-cli and react-native bundle components from the AppVeyor config * Removing x86 and ARM builds and x86 tests from AppVeyor config * Reverting to previous examples version
2016-11-02 21:47:41 +03:00
UpgradeLog.htm
#MonoDevelop
*.pidb
*.userprefs
#Tooling
_ReSharper*/
*.resharper
[Tt]est[Rr]esult*
*.sass-cache
WiniumDriver/
#Project files
[Bb]uild/
#Subversion files
.svn
# Office Temp Files
~$*
# vim Temp Files
*~
#NuGet
packages/
*.nupkg
*.nuget.props
*.nuget.targets
#Allow root packages folder though
!/packages
#ncrunch
*ncrunch*
*crunch*.local.xml
# visual studio database projects
*.dbmdl
#Test files
*.testsettings
#Other files
*.DotSettings
.vs/
*project.lock.json
jsconfig.json
package-lock.json
*.metaproj
*.metaproj.tmp
# VS Code
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
vnext/.vscode/*
#JavaScript files
*.jsbundle
2016-08-22 18:38:33 +03:00
# Visual C++ cache files
ipch/
*.ipch
2016-08-22 18:38:33 +03:00
*.aps
*.ncb
*.opendb
*.opensdf
*.sdf
*.cachefile
*.VC.db
*.VC.VC.opendb
# Build results
[Dd]ebugPublic/
[Rr]eleases/
x64/
x86/
bld/
[Ll]og/
*.binlog
# Certificates
*.pfx
# OpenCover
*_coverage.xml
Fix E2E Tests, add CI break on test failure, improve TreeDumpLibrary (#4585) Improve/refactor e2etest and TreeDumpLibrary in a number of ways: most importantly is that we've had test break but not fail the PR or CI - this is because wdio which we use as a test harness, does not set its exit code on success/failure, which is needed for Azure Pipelines to know whether it should fail the build or not. image Because we were blind to test failures, the outputs have drifted away from the original masters. I'm re-baselining them based on what we have today. Component owners should do a pass on the new masters to make sure nothing looks weird (e.g. ImageRTL still shows FlowDirection=LeftToRight). Filed #4589 to track this. changes the test app UI to provide links to the master and output files, and to diff the two. I wanted to launch vscode in diff mode for that but since we are a UWP app, the only way we can launch a program like that is to use a protocol handler, which vscode doesn't expose for diffing. Filed: Provide a protocol handler for diffing two files. For the time being, we'll copy the command line to launch vscode in diff mode for the two files. Adds the ability for the tree dump library to output json which will allow us to write tests that validate the output from the javascript side Adds logic for optionally output the name of elements. I plan to turn this and json output on soon but wanted to get a baseline PR/CI first. e2etest was crashing because of a bug in Switch: #4596 . Disabled that control in the test app for the time being. Added logic to the pipeline to capture crash dumps when e2etest app crashes Added checks to make sure we don't try to build/run the e2etest app in scenarios where it isn't really supported because the masters would not match (anything other than Release|x64 at 100% DPI). There are bugs tracking these limitations that we must fix before rtm: #4122 and #4619
2020-04-16 20:03:43 +03:00
tsdoc-metadata.json
*.dmp
*.pp
*.orig
# cppwinrt
nul
Stamp RNW Version into MSBuild Props (#8772) * Stamp RNW Version into MSBuild Props This change allows community modules to query against the RNW version used at compile-time. This creates a foundation for conditional compilation against new features/APIs/quirks. In order to calculate the new version number, existing DLL stamping code is run after the NPM package is published. Because we want to insert the version into the NPM package, we need to hook-in earlier. We use beachball prePublish hook as a mechanism to do this,. For clarity, we also commit the generated version to the repo, alongside the change to update package.json. Using beachball hooks requires us moving our root beachball config from our packge.json to a JS file. We previously mutated beachball args in the package.json, so we need to rewrite some of the code which generates beachball config. Props source of truth is a generated PropertySheet, exposed to internal and external projects. Preprocessor definitions mirroring the props are exposed by default to C++ apps/libs via external property sheets in the npm package. Stamping is done via a JS script and mustache templates (ala generator). This should make it easy to stamp versions into more file formats in the future (E.g. for runtime queries in C++/C#). * ordering * Add macros * Update beachball.config.js * yarn format * fiz * Update vnext/template/cpp-lib/src/pch.h * formatting and git * fix comparison * Use existing commit message for familiarity * Update TypeScript in package.json * parens and subsequent `yarn format` * inverted quotes
2021-10-24 12:01:05 +03:00
# Verdaccio
.verdaccio-db.json
# Graveyard of old packages (whose build-outputs may exist on disk after pull)
/packages/@rnw-bots/*
/packages/jest-environment-winappdriver/*
/packages/node-rnw-rpc/*
# midgard-yarn-strict
.store*/*