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.

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

Add Email type #1514

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add Email type #1514

wants to merge 1 commit into from

Conversation

arunpkm
Copy link

@arunpkm arunpkm commented Jul 28, 2023

Add Email type

@codecov
Copy link

codecov bot commented Jul 28, 2023

Codecov Report

Patch coverage has no change and project coverage change: -1.09% ⚠️

Comparison is base (f5aba2c) 96.01% compared to head (f034de9) 94.92%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1514      +/-   ##
==========================================
- Coverage   96.01%   94.92%   -1.09%     
==========================================
  Files          51       52       +1     
  Lines        1755     1775      +20     
==========================================
  Hits         1685     1685              
- Misses         70       90      +20     
Files Changed Coverage Δ
graphene/types/email.py 0.00% <0.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@erikwrede
Copy link
Member

Hey @arunpkm, what exactly are you trying to achieve with this PR? While the addition of a custom Email Scalar might make sense for a clean schema design, I'm not sure wether this should be part of the graphene implementation.
The specifics of this scalar may vary from company to company as there may be more granular email rules than those defined in the RFCs mentioned by you. Consequently, it might make sense to leave this to the individual developers.

Aside from that, it is important to provide test cases and up to date documentation in the PR. Currently, the scalar doesn't seem to be doing any email validation. What are your plans for this, going forward? LMK what you think 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants