101–110 of 411 posts
Earlier quoted context omitted.
I added "gender" (an IANA registered JWT claim) to my JWT payload schema and found Copilot will not provide any suggestions after that. Not on the same line, nor in the rest of the file. After removing the word gender entirely, it works again. https://www.iana.org/assignments/jwt/jwt.xhtml
-
Quoted post unavailable.
I encountered this when writing some scripts for Latin-language text processing (which dealt with grammatical gender). Thankfully the Latin-native term 'genus' passed the Copilot smell-test and I could continue with my work. I found it pretty amusing.
Earlier quoted context omitted.
I added "gender" (an IANA registered JWT claim) to my JWT payload schema and found Copilot will not provide any suggestions after that. Not on the same line, nor in the rest of the file. After removing the word gender entirely, it works again. https://www.iana.org/assignments/jwt/jwt.xhtml
-
Then you do it and report back when he's wrong.
Can we get a source for that? Because at the moment, it's just a comment made by a person on the internet with nothing backing it up...
So, I tested this locally and for the first time, immediately after using a variable named “gender”, it stopped suggesting. I wonder if this is to prevent it from accidentally processing PII or PHI data. Maybe someone else who didn’t get their account on some kind of cooldown can try it with “birthdate” or “DOB” or “SSN”. I highly doubt this has anything to do with gender being a controversial or blocked term for pol…
Help me out here, is the answer the official answer?
You can see it in the original link to the discussion: Answer selected by davecheney
Earlier quoted context omitted.
I added "gender" (an IANA registered JWT claim) to my JWT payload schema and found Copilot will not provide any suggestions after that. Not on the same line, nor in the rest of the file. After removing the word gender entirely, it works again. https://www.iana.org/assignments/jwt/jwt.xhtml
-
Besides the absurdity of the code crashing because of the word "gender". My problem and curiosity with all of this is... "What was going on in the head of the person writing the parser?" I mean, were they thinking that if someone is writing code, let's say, for a gender dropdown and it was only ["male", "female"], it would try to suggest to us to add 26 more genders instead (and worse, suggest a list of genders to ad…
> Would the intention be to correct us and popup a message saying "We suggest you add more genders so as not to displease the users of your product"??
You can just as easily assume that they don't want a dropdown with 26 additional genders to just pop up automatically. That would upset a lot of people, many of whom are in this thread. I think whoever wrote the code doesn't want to jump into a political shitstorm.