Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Schema validating for all provider occur during import regardless to the used provider #205

Open
gs202 opened this issue Feb 17, 2019 · 3 comments
Open

Schema validating for all provider occur during import regardless to the used provider #205

gs202 opened this issue Feb 17, 2019 · 3 comments
Assignees
@liiight
Labels
question
Projects
Switch to pydantic

Comments

@gs202
Copy link

gs202 commented Feb 17, 2019

DEBUG:notifiers:merging required dict into schema for pushover
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for pushover
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for telegram
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for gitter
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for pushbullet
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for join
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for hipchat
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for hipchat
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:merging required dict into schema for statuspage
DEBUG:notifiers:validating provider schema
DEBUG:notifiers:found a match for 'pushover', returning
DEBUG:notifiers:merging required dict into schema for pushover
DEBUG:notifiers:validating provider schema
@welcome
Copy link

welcome bot commented Feb 17, 2019

Thanks for opening your first issue here! Be sure to follow the issue template! 👋🐞👋

@liiight
Copy link
Owner

liiight commented Mar 11, 2019

This is intentional, however I will check to see if it has a performance penalty.

@liiight liiight self-assigned this Mar 11, 2019
@liiight
Copy link
Owner

liiight commented Jun 23, 2019

This will become redundant when switching to pydantic via #221

@liiight liiight closed this as completed Jun 23, 2019
@liiight liiight reopened this Jun 24, 2019
@liiight liiight removed the wontfix label Jun 24, 2019
@liiight liiight added this to To do in Switch to pydantic via automation Jun 24, 2019
@liiight liiight moved this from To do to Will become irrelevant in Switch to pydantic Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@liiight liiight

Labels
question
Projects
Switch to pydantic
  
Will become irrelevant
Milestone
No milestone
Development

No branches or pull requests
2 participants
@liiight @gs202