public/django-migration-linter
15
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
198 Commits 2 Branches 0 Tags
cb5d3991eec19a3172cd6d5e9c25bfdff2b4946a
Commit Graph
96 Commits
Author SHA1 Message Date
David Wobrock 19e54bba09 Refactor duplicated code in sql_analyser 2019-07-28 12:28:56 +02:00
David Wobrock 7215afa4a4 Fix line too long (flake8) 2019-07-28 12:28:56 +02:00
David Wobrock 85b9abdbc3 Display information that a problem has been found but ignored (and therefore the migration is considered ok) 2019-07-28 12:28:56 +02:00
David Wobrock af4b11c563 Document (README & CHANGELOG) and rename option to 'exclude-migration-tests' 2019-07-28 12:28:56 +02:00
vladmalynych 579e7c68b4 Fix linter issue 2019-07-28 12:28:56 +02:00
vladmalynych 6bbf2a653c Fix linter 'line too long' 2019-07-28 12:28:56 +02:00
Vladyslav Malynych 8eede82a38 Exclude not critical test (#2) 
* Exclude not critical test

* Add exclude-tests option

* Update documentation

* Clean forgotten print

* Improve Readme, with examples
 2019-07-28 12:28:56 +02:00
David Wobrock e93d4ec4c7 Bump to version 1.2.0 and update CHANGELOG.md 2019-07-10 10:26:42 +02:00
Victor Seva c0d33dd579 support setting DJANGO_PROJECT_FOLDER via --project-root-path 
settings file can be located in a subdirectory of the project
 2019-07-10 10:20:14 +02:00
David Wobrock 19fe5b75fe Add logic to ignore applied or unapplied migrations 2019-06-06 22:54:08 +02:00
David Wobrock ba0704ef3a Always load migrations from database: 
This enables us to detect if a migration has been applied to a certain database.
No matter if the migrations and detected from git or all, we always match them with the migrations found by Django.
 2019-06-06 22:54:08 +02:00
David Wobrock 3273f1bdc4 Add exclusive options for linting only applied or unapplied migrations 2019-06-06 22:54:08 +02:00
David Wobrock 42a83f18a0 Bump version to 1.1.0 and add note in CHANGELOG 2019-05-19 22:51:54 +02:00
David Wobrock e23e46e3d4 IgnoreMigrationOp: add class comment to explain purpose of no-op 2019-05-19 22:32:41 +02:00
Tobias Krönke dcaa52a4da simplify IgnoreMigration operation 2019-05-19 22:29:02 +02:00
Tobias Kroenke 08e15b84ae satisfy black 2019-05-19 22:29:02 +02:00
Tobias Kroenke 48cba37764 remove migration ignore sql analysis 2019-05-19 22:29:02 +02:00
Tobias Krönke 12d0b7e9be obey max line length 2019-05-19 22:29:02 +02:00
Tobias Krönke 44a0c83897 simplify any statement 2019-05-19 22:29:02 +02:00
Tobias Krönke 859b4b3b1b fix tests 2019-05-19 22:29:02 +02:00
Tobias Krönke 3f5b7bdb9b make should_ignore_migration check for IgnoreMigration operation 2019-05-19 22:29:02 +02:00
David Wobrock 3b2b2f91c2 Clean up unused code and comments 2019-05-12 15:50:03 +02:00
Felix 08dc26085b First check ignores then check cache 
This gives you the possibility to add a errornous migration
to the ignore list. On the seccond run the linter will
first use the ignore list and not the cache first.
 2019-05-12 15:32:57 +02:00
Felix b7c3ee38d7 Use logger.debug() for lowlevel information 
Effectivly this will prevent printing those lines
in a lot of default setups. Those lines make it quite
hard to understand the output of the liter.
 2019-05-12 15:32:57 +02:00
Felix 0bf7d5cc39 Use relative imports for easier in-place testing 2019-05-12 15:32:57 +02:00
David Wobrock e45e031820 Bump to 1.0.0 and update setup.py to drop command line usage 2019-05-12 15:32:57 +02:00
David Wobrock 484a775fda Linter Core: change lots of behaviour 
* Use the Django migration classes to manipulate these objects
this includes the discovery of migrations through the MigrationLoader
(instead of manually walking through the Django project and find the migrations through a regex)
and representing a Migration through the Django class.
* Get the SQL of a migration through a 'call_command' call of 'sqlmigrate'
That speeds up greatly the linter since we don't have to setup Django for each migration
* Add the database to the cache path
 2019-05-12 15:32:57 +02:00
David Wobrock 0eb584889a Add Django management command to launch the linter 2019-05-12 15:32:57 +02:00
David Wobrock 64c54b72d4 Bump to version 0.1.5 2019-04-21 12:53:13 +02:00
Taras Vozniuk fb0d7f07bc quite migration name to avoid failures of migration with space in the name 2019-04-21 12:47:17 +02:00
David-Wobrock 1245e7939d Bump to version 0.1.4 2019-02-24 18:19:49 +01:00
David-Wobrock 36e7dfaa0e Do not create cache folder if no-cache option 2019-02-24 18:18:45 +01:00
David-Wobrock c3c1af113c Handle postgresql alter column type 
ALTER TABLE table ALTER COLUMN column TYPE
 2019-02-24 15:55:05 +01:00
David-Wobrock 999ee2fa5e unrelated: fix some warnings and redundant elements 2019-02-24 15:55:05 +01:00
David-Wobrock f5a587c2be Fix split path function 
So it also works on windows
and does not return empty stuff
and update tests
 2019-02-24 15:55:05 +01:00
David-Wobrock f8d9ab777a Do not manually retrieve python interpreter path 
Instead of doing custom and wrong path detection, just
use sys.executable which does exactly that
 2019-02-24 11:04:21 +01:00
David-Wobrock 3591a4422a Bump to version 0.1.3 2019-02-03 19:39:31 +01:00
David Wobrock fea623630e Add --version option 2019-02-03 19:38:38 +01:00
Serj Zavadsky fbf0f44193 message string fix 2019-02-03 19:08:58 +01:00
Serj Zavadsky 0c66b1cdfa IgnoreMigration operation fix (postgres compatibility fix) 2019-01-29 17:08:42 +01:00
Serj Zavadsky 0ce615ff19 IgnoreMigration operation fix (postgres compatibility fix) 2019-01-29 16:52:08 +01:00
David Wobrock 4d68f7bac8 Bump version to 0.1.2 2019-01-21 22:08:57 +01:00
David Wobrock 009153fbf4 handle linting a project in pwd 
When calling "django-migration-linter ."
be able to handle it (especially with cache)
 2019-01-20 12:17:11 +01:00
David Wobrock 75c969c6a9 Revert "don't assume git root is django_path" 
This reverts commit c14f9aef37.
 2019-01-20 11:46:30 +01:00
Dat Hoang dca50b3afb Make sure file paths from git diff are relative to django_path instead of git repos root path 
Currently, the git diff command return file paths which are relative to git repos root path, which will cause invalid migration file path if git repos root path is different from django_path
 2019-01-20 11:43:33 +01:00
Victor Seva c14f9aef37 don't assume git root is django_path 
> DJANGO_SETTINGS_MODULE=xpbx.test django-migration-linter --no-cache $(pwd)/xpbx origin/2.4.1
> (customers, 0010_auto_20181026_1330)... Traceback (most recent call last):
>  File "/home/vseva/Env/xpbx/bin/django-migration-linter", line 11, in <module>
>    sys.exit(_main())
>  File "/home/vseva/Env/xpbx/lib/python3.6/site-packages/django_migration_linter/migration_linter.py", line 341, in _main
>    linter.lint_all_migrations(git_commit_id=args.commit_id)
>  File "/home/vseva/Env/xpbx/lib/python3.6/site-packages/django_migration_linter/migration_linter.py", line 145, in lint_all_migrations
>    self.lint_migration(m)
>  File "/home/vseva/Env/xpbx/lib/python3.6/site-packages/django_migration_linter/migration_linter.py", line 81, in lint_migration
>    md5hash = self.old_cache.md5(migration.abs_path)
>  File "/home/vseva/Env/xpbx/lib/python3.6/site-packages/django_migration_linter/cache.py", line 47, in md5
>    with open(path, "rb") as f:
> FileNotFoundError: [Errno 2] No such file or directory: '/home/vseva/Foehn/xpbx/xpbx/xpbx/customers/migrations/0010_auto_20181026_1330.py'

Fix: #37
 2019-01-17 20:40:32 +01:00
David-Wobrock f52bb3d9b8 Bump version to 0.1.1 2019-01-07 19:37:51 +01:00
Felix ab5536c8e7 Remove is_git_project from import 2019-01-07 12:25:57 +01:00
Felix 3ae4840e34 Merge branch 'master' into do-not-check-git-folder 2019-01-07 12:19:25 +01:00
Felix 92a686f13b Make imports relative 2019-01-05 22:24:33 +01:00