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

feat: Support is_secondary for domain updates to indicate that the subdomain is significant #308

Draft
wants to merge 1 commit into
base: v2
Choose a base branch
from

Conversation

yourtallness
Copy link
Contributor

@yourtallness yourtallness commented Jul 30, 2024

If is_secondary is true and the application supports it, then the full domain name provided will be stored as the domain, including any subdomain(s).

i.e. we will not be storying the eTLD+1 as the domain in case a subdomain is provided.

@yourtallness yourtallness requested a review from a team as a code owner July 30, 2024 11:56
@yourtallness yourtallness force-pushed the yourtallness/support_is_secondary_for_domain_updates branch from 27d7a00 to 684091a Compare July 30, 2024 12:07
…bdomain is significant

If `is_secondary` is `true` and the application supports it, then the full domain name provided will be stored as the domain, including any subdomain(s).

i.e. we will not be storing the eTLD+1 as the domain in case a subdomain is provided.
@yourtallness yourtallness force-pushed the yourtallness/support_is_secondary_for_domain_updates branch from 684091a to 8c60c7e Compare July 30, 2024 12:11
@yourtallness yourtallness marked this pull request as draft July 30, 2024 13:07
@dimkl dimkl changed the title feat: Support is_secondary for domain updates to indicate that the su… feat: Support is_secondary for domain updates to indicate that the subdomain is significant Aug 2, 2024
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.

3 participants