-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check validity of presets on startup #302
Conversation
for more information, see https://pre-commit.ci
@cymed Wow - nice new feature! |
For me this looks good. May be the (TEKSI) service providers want to comment also. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good input indeed.
|
||
pgservice = pg_layer.dataProvider().uri().service() | ||
msgs = tww_check_oid_prefix(pgservice) | ||
msgs.extend(tww_check_oid_prefix(pgservice)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cymed should that be msgs.extend(tww_check_fk_defaults(pgservice)
?
EDIT: And in general tww_validity_check
is never called. What is the idea behind? should we do those checks at plugin start / project opening?
On startup, we should check if the database is suitable for production