db-migrate 1.0.0-beta.2 → 1.0.0-beta.21

package/CHANGELOG.md

@@ -1,474 +0,0 @@
-# [1.0.0-beta.0](https://github.com/db-migrate/node-db-migrate/compare/v0.11.5...v1.0.0-beta.0) (2019-06-08)
-
-
-### Bug Fixes
-
-* **cwd:** addition of cwd missed function definition ([7c238a4](https://github.com/db-migrate/node-db-migrate/commit/7c238a4))
-* **plugin:** handle non existent dependencies and improve UX ([91b9da9](https://github.com/db-migrate/node-db-migrate/commit/91b9da9)), closes [#628](https://github.com/db-migrate/node-db-migrate/issues/628)
-* **plugin:** respect options cwd ([#618](https://github.com/db-migrate/node-db-migrate/issues/618)) ([3a8a09f](https://github.com/db-migrate/node-db-migrate/commit/3a8a09f))
-* **reset:** regression introduced in check functionality ([61ca5bb](https://github.com/db-migrate/node-db-migrate/commit/61ca5bb)), closes [#552](https://github.com/db-migrate/node-db-migrate/issues/552)
-* **scope:** new scoping errored out when using templates ([b2421e3](https://github.com/db-migrate/node-db-migrate/commit/b2421e3))
-* **utils:** resolve when returned null ([68361fe](https://github.com/db-migrate/node-db-migrate/commit/68361fe))
-* **walker:** rename interface to Interface ([6234d42](https://github.com/db-migrate/node-db-migrate/commit/6234d42))
-
-
-### Features
-
-* **chain:** add step chaining ([8203c55](https://github.com/db-migrate/node-db-migrate/commit/8203c55))
-* **error handling:** added advanced error handling and rollback ([aa13a35](https://github.com/db-migrate/node-db-migrate/commit/aa13a35))
-* **learning:** add db learning ([d5c9aa1](https://github.com/db-migrate/node-db-migrate/commit/d5c9aa1))
-* **migration:** add support for first basic options on new schema ([d891628](https://github.com/db-migrate/node-db-migrate/commit/d891628))
-* **schemav2:** add foreignKey support on tables ([3dd7158](https://github.com/db-migrate/node-db-migrate/commit/3dd7158))
-* **state:** add state manager and adjust driver functions ([10c3f1a](https://github.com/db-migrate/node-db-migrate/commit/10c3f1a))
-* **statemanager:** add first edition of state manager ([6dc4d3b](https://github.com/db-migrate/node-db-migrate/commit/6dc4d3b)), closes [#538](https://github.com/db-migrate/node-db-migrate/issues/538)
-
-
-
-## [0.11.6](https://github.com/db-migrate/node-db-migrate/compare/v0.11.5...v0.11.6) (2019-06-08)
-
-
-### Bug Fixes
-
-* **cwd:** addition of cwd missed function definition ([fae85cf](https://github.com/db-migrate/node-db-migrate/commit/fae85cf))
-* **plugin:** allow no package.json ([f27dce0](https://github.com/db-migrate/node-db-migrate/commit/f27dce0))
-* **plugin:** handle non existent dependencies and improve UX ([006ef5e](https://github.com/db-migrate/node-db-migrate/commit/006ef5e)), closes [#628](https://github.com/db-migrate/node-db-migrate/issues/628)
-* **plugin:** respect options cwd ([#618](https://github.com/db-migrate/node-db-migrate/issues/618)) ([3dae762](https://github.com/db-migrate/node-db-migrate/commit/3dae762))
-
-
-<a name="0.11.5"></a>
-## [0.11.5](https://github.com/db-migrate/node-db-migrate/compare/v0.11.4...v0.11.5) (2019-01-06)
-
-
-### Bug Fixes
-
-* **db:** set exit code as 1 only on error ([3148cc9](https://github.com/db-migrate/node-db-migrate/commit/3148cc9))
-* Added warning on plugin loading failure ([fcffd62](https://github.com/db-migrate/node-db-migrate/commit/fcffd62))
-* **lgtm:** fix errors ([4cd5558](https://github.com/db-migrate/node-db-migrate/commit/4cd5558))
-
-
-
-<a name="0.11.3"></a>
-## [0.11.3](https://github.com/db-migrate/node-db-migrate/compare/v0.11.2...v0.11.3) (2018-09-08)
-
-
-### Bug Fixes
-
-* **db:** create and drop always result in exit code 1 ([d32644c](https://github.com/db-migrate/node-db-migrate/commit/d32644c)), closes [#550](https://github.com/db-migrate/node-db-migrate/issues/550)
-
-
-
-<a name="0.11.2"></a>
-## [0.11.2](https://github.com/db-migrate/node-db-migrate/compare/v0.10.0...v0.11.2) (2018-09-05)
-
-
-### Bug Fixes
-
-* **check:** fix check via API not passing results to the callback ([b743696](https://github.com/db-migrate/node-db-migrate/commit/b743696))
-* **ci:** add ignores for backported features ([21c3eb9](https://github.com/db-migrate/node-db-migrate/commit/21c3eb9))
-* **db:** wrong reference to connect causes db:create to fail ([991ee76](https://github.com/db-migrate/node-db-migrate/commit/991ee76)), closes [#520](https://github.com/db-migrate/node-db-migrate/issues/520)
-* **exitCode:** wrong check for existence fixed ([3c6fc33](https://github.com/db-migrate/node-db-migrate/commit/3c6fc33))
-* **exitCode:** wrong exit code on db methods ([486cb78](https://github.com/db-migrate/node-db-migrate/commit/486cb78)), closes [#534](https://github.com/db-migrate/node-db-migrate/issues/534)
-* **insert:** add missing insert entry to interface ([7ca2f56](https://github.com/db-migrate/node-db-migrate/commit/7ca2f56)), closes [#542](https://github.com/db-migrate/node-db-migrate/issues/542)
-* Update dependency `rc` to latest version ([b343add](https://github.com/db-migrate/node-db-migrate/commit/b343add))
-* **log:** error ended up in unreadable errors ([16512f6](https://github.com/db-migrate/node-db-migrate/commit/16512f6)), closes [#524](https://github.com/db-migrate/node-db-migrate/issues/524) [#521](https://github.com/db-migrate/node-db-migrate/issues/521)
-* **progamableApi:** cmdOptions get passed into setDefaultArgv now ([cb88b58](https://github.com/db-migrate/node-db-migrate/commit/cb88b58))
-* **reset:** regression introduced in check functionality ([b94db96](https://github.com/db-migrate/node-db-migrate/commit/b94db96)), closes [#552](https://github.com/db-migrate/node-db-migrate/issues/552)
-* **switchDatabase:** no error was thrown on scope switch ([392d88c](https://github.com/db-migrate/node-db-migrate/commit/392d88c)), closes [#470](https://github.com/db-migrate/node-db-migrate/issues/470)
-* update vulnerable pack 'deep-extend' and OOD deps ([8e13c7f](https://github.com/db-migrate/node-db-migrate/commit/8e13c7f))
-
-
-### Features
-
-* **check:** add check functionality to determine migrations to run ([56acdb9](https://github.com/db-migrate/node-db-migrate/commit/56acdb9))
-* **contribution:** enrich contribution instructions ([2cd0578](https://github.com/db-migrate/node-db-migrate/commit/2cd0578)), closes [#549](https://github.com/db-migrate/node-db-migrate/issues/549)
-* **contribution:** enrich contribution instructions, issues ([5ee386b](https://github.com/db-migrate/node-db-migrate/commit/5ee386b))
-* **issuetemplate:** added a github issue template ([3c0fcbf](https://github.com/db-migrate/node-db-migrate/commit/3c0fcbf))
-* **progamableApi:** CMD options can be passed programatically now ([fd8562e](https://github.com/db-migrate/node-db-migrate/commit/fd8562e))
-* **progamableApi:** using const now ([d761ebf](https://github.com/db-migrate/node-db-migrate/commit/d761ebf))
-
-
-
-<a name="0.11.1"></a>
-## [0.11.1](https://github.com/db-migrate/node-db-migrate/compare/v0.11.0...v0.11.1) (2018-04-10)
-
-
-### Bug Fixes
-
-* **reset:** regression introduced in check functionality ([d8a735d](https://github.com/db-migrate/node-db-migrate/commit/d8a735d)), closes [#552](https://github.com/db-migrate/node-db-migrate/issues/552)
-
-
-
-<a name="0.11.0"></a>
-# [0.11.0](https://github.com/db-migrate/node-db-migrate/compare/v0.10.7...v0.11.0) (2018-04-10)
-
-
-### Features
-
-* **check:** add check functionality to determine migrations to run ([93e9f18](https://github.com/db-migrate/node-db-migrate/commit/93e9f18))
-
-
-
-<a name="0.10.7"></a>
-## [0.10.7](https://github.com/db-migrate/node-db-migrate/compare/v0.10.6...v0.10.7) (2018-03-27)
-
-
-### Bug Fixes
-
-* **progamableApi:** cmdOptions get passed into setDefaultArgv now ([ebdd75d](https://github.com/db-migrate/node-db-migrate/commit/ebdd75d))
-
-
-
-<a name="0.10.6"></a>
-## [0.10.6](https://github.com/db-migrate/node-db-migrate/compare/v0.10.5...v0.10.6) (2018-03-21)
-
-
-### Bug Fixes
-
-* **ci:** add ignores for backported features ([53dedc2](https://github.com/db-migrate/node-db-migrate/commit/53dedc2))
-
-
-### Features
-
-* **contribution:** enrich contribution instructions ([93b5cea](https://github.com/db-migrate/node-db-migrate/commit/93b5cea)), closes [#549](https://github.com/db-migrate/node-db-migrate/issues/549)
-* **contribution:** enrich contribution instructions, issues ([d87a734](https://github.com/db-migrate/node-db-migrate/commit/d87a734))
-* **progamableApi:** CMD options can be passed programatically now ([69d7605](https://github.com/db-migrate/node-db-migrate/commit/69d7605))
-* **progamableApi:** using const now ([a69e221](https://github.com/db-migrate/node-db-migrate/commit/a69e221))
-
-
-
-<a name="0.10.4"></a>
-## [0.10.4](https://github.com/db-migrate/node-db-migrate/compare/v0.10.3...v0.10.4) (2018-02-06)
-
-
-### Bug Fixes
-
-* **insert:** add missing insert entry to interface ([899b8bc](https://github.com/db-migrate/node-db-migrate/commit/899b8bc)), closes [#542](https://github.com/db-migrate/node-db-migrate/issues/542)
-
-
-
-<a name="0.10.3"></a>
-## [0.10.3](https://github.com/db-migrate/node-db-migrate/compare/v0.10.2...v0.10.3) (2018-02-03)
-
-
-### Bug Fixes
-
-* **db:** wrong reference to connect causes db:create to fail ([991ee76](https://github.com/db-migrate/node-db-migrate/commit/991ee76)), closes [#520](https://github.com/db-migrate/node-db-migrate/issues/520)
-* **exitCode:** wrong check for existence fixed ([3c6fc33](https://github.com/db-migrate/node-db-migrate/commit/3c6fc33))
-* **exitCode:** wrong exit code on db methods ([486cb78](https://github.com/db-migrate/node-db-migrate/commit/486cb78)), closes [#534](https://github.com/db-migrate/node-db-migrate/issues/534)
-* **log:** error ended up in unreadable errors ([16512f6](https://github.com/db-migrate/node-db-migrate/commit/16512f6)), closes [#524](https://github.com/db-migrate/node-db-migrate/issues/524) [#521](https://github.com/db-migrate/node-db-migrate/issues/521)
-* **switchDatabase:** no error was thrown on scope switch ([392d88c](https://github.com/db-migrate/node-db-migrate/commit/392d88c)), closes [#470](https://github.com/db-migrate/node-db-migrate/issues/470)
-
-
-### Features
-
-* **issuetemplate:** added a github issue template ([3c0fcbf](https://github.com/db-migrate/node-db-migrate/commit/3c0fcbf))
-
-
-
-<a name="0.10.2"></a>
-## [0.10.2](https://github.com/db-migrate/node-db-migrate/compare/v0.10.1...v0.10.2) (2017-12-01)
-
-
-### Bug Fixes
-
-* **log:** error ended up in unreadable errors ([97de65d](https://github.com/db-migrate/node-db-migrate/commit/97de65d)), closes [#524](https://github.com/db-migrate/node-db-migrate/issues/524) [#521](https://github.com/db-migrate/node-db-migrate/issues/521)
-
-
-
-<a name="0.10.1"></a>
-## [0.10.1](https://github.com/db-migrate/node-db-migrate/compare/v0.10.0...v0.10.1) (2017-11-27)
-
-
-### Bug Fixes
-
-* **db:** wrong reference to connect causes db:create to fail ([56cb75a](https://github.com/db-migrate/node-db-migrate/commit/56cb75a)), closes [#520](https://github.com/db-migrate/node-db-migrate/issues/520)
-
-## 0.10.0
-
-Note:
-
-This is a cornerstone release. It provides groundwork for many things to come and has worked
-on stability and flexibility, while mostly retaining backwards compatibility.
-
-This release was a rewrite of nearly the whole module. However backwards compatibility 
-was mostly preeserved. Bug fixes wont be listed for this release, all subsequent releases
-will follow the angular standard to automatically generate changelogs.
-
-New Features:
- - Sync
- - Driverless Core
- - Plugin Hooks and overwrites
- - Adjusted migration schema, to allow specific setup routines
- - Version migration schemas itself for future iterations
- - Promise style migrations
- - Programmatic API
- - Restructered major parts of db-migrate
- - Transactional migrations
- - New configuration options
-
-Find a full list of features added here:
-
-https://github.com/db-migrate/node-db-migrate/issues?utf8=%E2%9C%93&q=milestone%3Av0.10.0
-
-# Old Changelogs
-
-## 0.1.0
-
-New Features:
-
-  - Added support for PostgreSQL (via Roman Ostolosh)
-
-## 0.1.1
-
-Fix:
-
-  - Fixed migration table creation for PostgreSQL (via Brandon Keene)
-
-## 0.1.2
-
-Fix:
-
-  - Fix string type for PostgreSQL #14 (via Matt Huggins)
-  - Fix renameTable method for PostgreSQL #15 (via Roman Ostolosh)
-
-## 0.1.3
-
-Fix:
-  - Respect column length specification on column defs #16 (via Matt Huggins)
-  - Allow default environment to be dev or development #17 (via Matt Huggins)
-
-## 0.1.4
-
-Fix:
-  - Fix migration table creation error on PostgreSQL >= 9.1 #20
-  - Document length property on columns #19 (via Glen Mailer)
-
-## 0.1.5
-
-Fix:
-  - Add testing for all supported database drivers
-  - Fix dropTable on PostgreSQL #21
-  - Implement removeColumn and changeColumn for MySQL
-
-## 0.2.0
-
-New Feature:
-  - Expose currently running environment name #22
-  - Added an insert method to the API #23
-  - Add support for unknown column data types #34
-
-Fix:
-  - Fixed error creating migration table #26
-  - Fixed removeIndex error in MySQL #37
-  - Fixed issue with tests using too many connections under PostgreSQL
-  - Fixed error running migrations under sqlite3 #27
-
-## 0.2.1
-
-Improvement:
-  - Added compatibility for mysql-2.0.0-alpha driver #25
-
-## 0.2.2
-
-Fix:
-  - Fix default value error when using Postgres #43
-
-## 0.2.3
-
-Fix:
-  - Fix error when using mysql-2.0.0-alpha3 driver #44
-
-## 0.2.4
-
-Fix:
-  - Use --migrations-dir option when specified #47
-  - Handle unique constraints in changeColumn() for postgres #46 (via @ryanmeador)
-
-## 0.2.5
-
-Fix:
-  - Fix randomly occuring migration sorting error on empty db #51
-
-## 0.2.6
-
-Fix:
-  - Fix db.removeIndex for MySQL #42 (via @aprobus)
-  - Workaround for node-mysql bug felixge/node-mysql#289 #54 (via
-    @aprobus)
-
-## 0.2.7
-
-Fix:
-  - Support process.env.DATABASE_URL for postgres, for use with Heroku #57 (via @garth)
-
-## 0.2.8
-
-Improvement
-  - Added support for additional MySQL data types #58 (via @jpravetz)
-
-## 0.3.0
-
-Improvement:
-  - Added support for MySQLs LONGTEXT #62 (via @joeferner)
-
-New Feature:
-  - Added dry-run support for migrations #55 (via @joeferner)
-
-## 0.3.1
-
-Improvement:
-  - Added support for boolean data type #66 (via @trojanowski)
-
-## 0.3.2
-
-Fix
-  - Update error message when using an invalid data type #67 (via @swang)
-
-## 0.4.0
-
-New Feature:
-  - Added support for renameColumn in MySQL #80 (via @akinnunen)
-
-Improvement:
-  - Added --version flag #73 (via @mcandre)
-  - Lazily require migrations #77, #78 (via @btakita)
-
-Fix
-  - Fixed typo in lib/driver/pg.js for BLOB datatype #76
-
-## 0.4.1
-
-Improvement:
-  - Add support for BIGINT data type #81
-
-## 0.4.2
-
-Improvement:
-	- Superficial changes based on JSHint report #85, #88 (via @mcandre)
-	- Let DATABASE_URL configure any database #90 (via @pwnall)
-
-Fix:
-	- Fix for postgres driver blindly recreating the migrations table #89 (via @sgibbons)
-	- Mitigate `npm test` permission error #95 (via @mcandre)
-
-## 0.5.0
-
-New Feature:
-	- Support for database URLs in database.json #103 (via @miguelgrinberg)
-	- Option to use native Postgres client #106 (via @olalonde)
-
-Improvement:
-	- Updated README.md documentation #98 (via @acco)
-
-## 0.5.1
-
-Improvement:
-  - Add a force-exit flag #108 (via @codeaholics)
-  - Provide close callback for MySQL driver #107 (via @codeaholics)
-
-## 0.5.2
-
-Fix:
-  - Add ability to create camel-cased column names for PostgreSQL #111 (via @virpool)
-  - Add ability to make a unique index #110 (via @codeaholics)
-
-## 0.5.3
-
-Fix:
-  - Fixed bug setting default values to values that are falsy #114 (via @wbrady)
-
-## 0.5.4
-
-Fix:
-  - Add backticks to MySQL driver #114 (via @mstorgaard)
-
-## 0.6.0
-
-New Feature:
-  - Support varargs in runSql, all on mysql driver #119 (via @Gloridea)
-  - Load Environment Variables specified in config file #118 (via @codyhanson)
-  - Added CoffeeScript support for migrations #116 (via @DeniSix)
-
-Improvement:
-  - Added date type for sqlite3 #121 (via @mrcsparker)
-
-Fix:
-  - Fix postgres issue with camelCased column name definition #125 (via @virpool)
-
-## 0.6.1
-
-Fix:
-  - Fix two regressions related to runSql not accepting params as an
-    array #127, #128
-
-## 0.6.2
-
-Fix:
-  - Fix add index downcasing table name in MySQL #126 (via @noazark)
-  - Fix dry run on first migration #132 (via @jgoyon)
-
-Improvement:
-  - Add decimal data type support
-
-## 0.6.3
-
-Fix
-  - Fix postgres issue with camelCased column name during insert #137 (via @tone81)
-
-## 0.6.4
-
-Improvement:
-  - Handle more than one single quote in string literals in a portable way #151 (via @szywon)
-  - added date, char and smallint types for pg #150 (via @FabricioFFC)
-  - better error handling for broken database.json files #149 (via @acruikshank)
-
-Fix:
-  - Make compatible with coffee-script 1.7 #147 (via @jinze)
-  - docs: the exports.down fn gets (db, callback) as params #144 (via @alxndr)
-  - Fix for multiple single quotes in a string #143
-
-## 0.7.0 (2014-08-01)
-
-Improvement:
-  - Externalize db configuration for tests #180 (via @dlaxar)
-  - Tightening up some js syntax #179 (via @paulomcnally)
-  - Change down migrations to execute in order they were run #178 (via @ajkerr)
-  - addForeignKey and removeForeignKey added to mysql #174 (via @JohanObrink)
-  - Add ability to use .env file for config if present #170 (via @bvalosek)
-
-## 0.7.1 (2014-08-05)
-
-Improvement:
-  - allow addColumn to create primary keys #183 (via @lourenzo)
-
-## 0.8.0 (2014-11-25)
-
-Improvement:
-  - Allow changing schema for Postgres #153 (via @zoips)
-  - Enable autoincrement even when emitting primary key #157 (via @kkurahar)
-  - New option to auto-generate SQL files #160 (via @tuliomonteazul)
-  - Allow dry run to work when there is no migration table #166 (via @jjshoe)
-  - Add support for Postgres driver in DATABASE_URL #188 (via @saxicek)
-  - Use JSON.stringify on non-string objects #185 (via @G3z)
-  - Add back quotes around foreign key name #189 (via @sitnin)
-  - Mask passwords in verbose logging #195 (via @Crotery)
-
-## 0.9.0 (2015-02-14)
-
-Improvement:
-  - Documentation improvements #223, #210, #199, #158, #138 (Tobias Gurtzick @wzrdtales)
-  - Multiple Scope Support (@wzrdtales)
-  - Fixed bug by generalizing the usage of automatic quoting over all current drivers #204, #140, #155 (@wzrdtales)
-  - MongoDB Driver #205, 217 (Tom Calfish @toymachiner62)
-  - Fix error db-migrate command not found, make db-migrate usable as global module #210, #138 (@wzrdtales)
-  - Add coffeescript template #208 (@richardfickling)
-  - Support for Postgresql foreign keys #203 (@dlaxar and @NOtherDev)
-  - Add support to create new databases and schemas #196, #202 (@wzrdtales)
-  - Add ability to change the migration table name #192 (@wzrdtales)
-  - Fix bug with column unique specification #123 (@wzrdtales)
-  - Added support for constraints on columns #35 (@wzrdtales)
-  - Added reset functionality #221 (@wzrdtales)
-  - Aliased "default" option to "env" #219 (@wzrdtales)
-
-Full log at:
-  [v0.9.0](https://github.com/kunklejr/node-db-migrate/issues?q=milestone%3Av0.9.0)

package/CODE_OF_CONDUCT.md

@@ -1,46 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at dbmigrate@wizardtales.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

package/CONTRIBUTING.md

@@ -1,81 +0,0 @@
-# Contributing by opening an Issue or Discussing
-
-Whenever you find a bug, which you do not have the time to fix, it is still important
-to get your input. Same goes for feature suggestions and everything else that helps
-a project to get better.
-
-Here are a few points to consider before creating an issue or discussing within one:
-
-1. Make sure you have proper description of your problem or what exactly you want:
-
-We have issue templates in place that should help you with this one and this is really
-important, since we may not just agree with you, if we don't understand your use case.
-
-2. Be constructive and before you post think once more if this is going to waste the maintainers
-   time, or if it is going to actually help them.
-
-Since being constructive, is a big vague, here some simple points that should help you:
-
-2.1. Just stating something is wrong, is not constructive.
-
-When you've got the feeling something is wrong, try to understand first if it is really wrong
-and if it is make suggestions on how to improve, or even better open a PR and make the open source
-world once again even better!
-
-2.2. "Does not work", is not a proper problem description
-
-Neither is, "see title". When you follow the issue template and provide all informations asked for
-you should be pretty fine, in providing us exactly the information we need to help you.
-
-2.3. Follow the CoC and contribute, not attack
-
-An example when you're not contributing, but attacking is, should you just impose you're right
-and you should be followed. It is always about the dialogue, that makes the difference. After all
-you should be fine, by just using your common sense.
-
-# Contributing a Pull Request
-
-Without pull requests from generous people like you, this project
-wouldn't be what it is today. You are planning to contribute aren't you?
-If so, here's a quick guide to creating a great pull request for
-this project:
-
-1. Fork the repo.
-
-2. Copy the test/db.config.example.json to test/db.config.json
-
-3. Run the tests. Pull requests without tests are much less likely to be
-   merged, and it's great to know you're starting with a clean slate: `npm test`.
-   Be sure to check the README for setting up your test databases first.
-
-4. Add a test for your change. Refactoring and documentation changes
-   require no new tests. If you are adding functionality or fixing a bug,
-   please include a test.
-
-5. Make the test pass.
-
-6. Create a commit that complies with our conventions, which you can view
-   [here](https://github.com/conventional-changelog/conventional-changelog/tree/35e60b5be6027fb2784c5103eee111f6f99b045e/packages/conventional-changelog-angular)
-   and last but not least also comply to the [DCO](https://github.com/probot/dco#how-it-works).
-   Which easiest work with just commiting via `git commit -s -m 'your commit message'`.
-
-7. Push to your fork and submit a pull request.
-
-At this point you're waiting on me. In a perfect world I'd commit to
-responding to your request in some short period of time. Unfortunately,
-I'm not able to do that. You'll most likely see me work off several pull
-requests in batches. I may suggest some changes or improvements or alternatives
-at that time. Please don't consider the feedback as a lack of
-appreciation for your time and effort. It most certainly is not.
-
-Some things that will increase the chance that your pull request is accepted,
-are:
-
-* Include good tests
-* Keep the changeset small
-* Stick to existing code conventions
-* Update the documentation, examples elsewhere, guides,
-  whatever is affected by your contribution
-
-See my [pull request etiquette](http://kunkle.org/blog/2013/07/10/pull-request-etiquette/)
-post for more contribution tips.

package/Makefile

@@ -1,8 +0,0 @@
-test:
-	@node node_modules/lab/bin/lab -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-test-cov:
-	@node node_modules/lab/bin/lab -t 66 -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-test-cov-html:
-	@node node_modules/lab/bin/lab -r html -o coverage.html -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-
-.PHONY: test test-cov test-cov-html

package/commitlint.config.js

@@ -1 +0,0 @@
-module.exports = { extends: ['@commitlint/config-angular'] };

package/lib/commands/transition.js

@@ -1,5 +0,0 @@
-'use strict';
-
-module.exports = function (internals) {
-  require('../transitions/transitioner.js')(internals);
-};

package/lib/transitions/1.js

@@ -1,30 +0,0 @@
-/**
- * Our first transition is actually the removal of globals and
- * introducing the setup routine.
- * Thus the body of this transition is just an empty function, but displays
- * as all transitions an explanation to the user.
- */
-module.exports = {
-  transition: function () {},
-
-  message: function () {
-    console.log(
-      'Congratulations!\n\n' +
-        'You just migrated from protocol 0 to 1!\n' +
-        'What does that mean for you?\n' +
-        'Quite simple, from 0 to 1 we introduced the setup function and we ' +
-        'deprecated some globals, like async or dbm. What this transition does is' +
-        ' grabbing your migrations, replacing the async and dbm definitions and ' +
-        'inserting the setup body if not present.\n' +
-        'It might be possible, that you still run into errors, for example if ' +
-        'you already have had a setup body, it wont be replaced and you might ' +
-        'be missing the default routine of the setup, which provides for example ' +
-        'the dataTypes to your migration.\n\n' +
-        'What do I need to do now?\n' +
-        'Try to rexecute all of your migrations and watch if you run into any ' +
-        'Errors, if you encounter any, you need to manually fix those ' +
-        "problems. But don't worry, this protocol transitions happen very " +
-        'rarely!\n'
-    );
-  }
-};

package/lib/transitions/ask.js

@@ -1,22 +0,0 @@
-var prompt = require('prompt');
-
-function ask (schema, callback) {
-  console.log('Starting transition helper...\n');
-
-  prompt.start();
-
-  prompt.get(schema, function (err, result) {
-    if (err) {
-      return callback(err);
-    }
-
-    if (result.safe === 'n') {
-      console.log('Aborted transition helper!');
-      callback(new Error('Aborted transition.'));
-    } else {
-      callback(null, result);
-    }
-  });
-}
-
-module.exports = ask;