This repository was archived by the owner on Oct 11, 2022. It is now read-only.
Dont use firstnamelastname on empty user profile thread feed #4707
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
Deploy after merge (delete what needn't be deployed)
Ref https://spectrum.chat/?t=331e064e-72c2-4143-adc3-bfa64bc5dce8
We shouldn't really ever use
firstNameorlastNameanywhere in the frontend since people can't actually change it right now - it's just imported from an auth flow. I did a cursory check across all our servers for uses of these fields that could break, but I think this is the main one (the only other case being in the user onboarding where we use the fields to try and guess at a username suggestion)