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

Removed unnecessary text under verified studentstatus #4487

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

Conversation

magnusbrecke
Copy link
Contributor

@magnusbrecke magnusbrecke commented Feb 27, 2024

Description

Removed unnecessary text under verified studentstatus since it was basically the same information as the box over, and it looked very untidy

Result

Before:

Skjermbilde 2024-02-27 kl  21 12 06

After:

Skjermbilde 2024-02-27 kl  21 11 30

  • Changes look good on both light and dark theme.
  • [ x] Changes look good with different viewports (mobile, tablet, etc.).
  • [ x] Changes look good with slower Internet connections.

Testing

  • [x ] I have thoroughly tested my changes.

Please describe what and how the changes have been tested, and provide instructions to reproduce if necessary.


Resolves ... ABA-641

@magnusbrecke magnusbrecke requested review from ivarnakken and a team February 27, 2024 20:14
@github-actions github-actions bot added the review-needed Pull requests that need review label Feb 27, 2024
Comment on lines 156 to 158
<Button success onClick={() => performStudentAuth()}>
Verifiser med FEIDE
</Button>
Copy link
Contributor

@Bestem0r Bestem0r Feb 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should be hidden when verified? @ivarnakken @magnusbrecke

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that would be reasonable. The FEIDE knapp has no purpose right now the way I see it. What do you think Ivar?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No users have to verify themselves roughly every year if I remember correctly. So a user should definitely be able to verify whenever they want, especially if there are updates in their FEIDE user info, but perhaps we can change the wording to "Verifiser med FEIDE på nytt" or something?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is basically what the info text you removed said - so we should maybe update the text in the blue info card above slightly so that it is clear to the user that they are currently verified and that they can verify again if they want to (or need to, I guess).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming the feide-implementation is still only putting people in 1st/4th grade if they are not in a grade as this linear issue is still open: https://linear.app/abakus-webkom/issue/ABA-534/semi-auto-grade-selection-for-feide-verification

And if that's the case, wouldn't it be fine to hide the button? Currently re-verifying will not make any type of functional changes on the webapp (afaik), so I see no reason to encourage users to re-verify as of now.

Although if we get to a point where feide-verification will actually do something useful (other than avoiding having to check your studmail) (or if we are actually at that point right now and I'm just unaware), I would suggest the following;

{isVerified && <SuccessCard />} // title: Du er verifisert som student
{!isVerified && <DangerCard />} // title: Du er ikke verifisert som student

{isVerified && <WarningCard />}
/* title: Ønsker du å endre trinn eller studie?
Trykk på "Verifiser med FEIDE" for å hente nye opplysninger. 
Fungerer ikke dette? Send en mail til [email protected], ...resten av beskrivelsen av krav...*/

<VerifyButton>Verifiser med FEIDE</VerifyButton>

Soo for now I'm positive to remove the button if you're already verified. And maybe splitting the InfoCard that we currently use into a SuccessCard and a WarningCard as in my mock example

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And regarding re-verifying every year.. If we at some point actually implement that (right now the feide-verification does not impact any of your rights on the website - the only "useful" part of it is that you get added to one of the student groups), it shouldn't say "Du er verifisert som student" if you have to re-verify.. Then it should say something like "Du må verifisere student-statusen din på nytt" in some sort of a danger-card style.

And of course make the button visible again - unless the semi-auto-grade selection is implemented.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that's true - we should definitely make the verification useful ..

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to slide in some background here. You are right on that when you are verified, you don't really need to reverify ever, except in some cases:

You changed from komtek <-> data. I believe (although I'm not 💯% sure) that I added logic for changing you study using the verification.

Its also here because when is student==false, the verification is done, but unsuccessfully, and then you have the option to try again later when studweb is correct or whatever. The text under the button was thought to explain why it's there so people don't get super confused, although I see how it might do the opposite. I also left it there when you are successfully verified because of the same reasons above I believe. I.e removing the button would remove the option to try again, making it possible to end up in a state where you user verification status is broken/stuck.

@magnusbrecke magnusbrecke self-assigned this Feb 27, 2024
@magnusbrecke magnusbrecke added small-fix Pull requests that fix something small changes-requested Pull requests with requested changes chore Pull requests that does something "boring", yet important, e.g. cleaning up code labels Feb 27, 2024
Copy link
Member

@jonasdeluna jonasdeluna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! I think we should probably still show some confirmation that you're already verified (assuming we don't).

This is a bit unrelated but branch names should be all lower case; written in kebab case :)
PR title and branch name should also be in imperative, so something like "fix-student-verification" perhaps.
Again, this is unrelated to the actual work but makes the project overall more concise and adhere to standards :)

@falbru
Copy link
Contributor

falbru commented Feb 27, 2024

Awesome work 🤩

@ivarnakken
Copy link
Member

This is a bit unrelated but branch names should be all lower case; written in kebab case :)
PR title and branch name should also be in imperative, so something like "fix-student-verification" perhaps.
Again, this is unrelated to the actual work but makes the project overall more concise and adhere to standards :)

Related to this, I suggest reading the CONTRIBUTING.md

@magnusbrecke
Copy link
Contributor Author

@ivarnakken what is the conclusion on this pr?

@ivarnakken
Copy link
Member

@ivarnakken what is the conclusion on this pr?

Like the others point out, we should still say that the user can verify themselves again to update their status. They don't necessarily have to write a mail to us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes-requested Pull requests with requested changes chore Pull requests that does something "boring", yet important, e.g. cleaning up code review-needed Pull requests that need review small-fix Pull requests that fix something small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants