Skip to content

[$40] Settings > Account > My Account: Entering incorrect current password to change the password won't show any validation #2056

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

Closed
codejamtc opened this issue Mar 15, 2019 · 21 comments

Comments

@codejamtc
Copy link
Collaborator

image

  1. Open the application and login as Manager (pshah_manager)
  2. Hover over the profile avatar > Click Settings
  3. Click Account Tab > My Account
  4. Enter 'qwert123@' to the new password field
  5. Enter '123456' as Current password
  6. Click Change Password

Actual: Entering incorrect current password to change the password won't show any validation

Expected: Should show a validation because the current password entered into the field is incorrect

Reproducibility Rate: 3/3

Environment: HP Pavilion x360 14 inch; Windows 10 | Browser: Google Chrome 73.0.3683.75

@ThomasKranitsas ThomasKranitsas changed the title Settings > Account > My Account: Entering incorrect current password to change the password won't show any validation [$40] Settings > Account > My Account: Entering incorrect current password to change the password won't show any validation Mar 20, 2019
@ThomasKranitsas
Copy link
Contributor

Contest https://www.topcoder.com/challenges/30086772 has been created for this ticket.

This is an automated message for thomaskranitsas via Topcoder X

@ThomasKranitsas
Copy link
Contributor

Contest https://www.topcoder.com/challenges/30086772 has been updated - the new changes has been updated for this ticket.

This is an automated message for thomaskranitsas via Topcoder X

@RAJKUMARRRR
Copy link

i want to work on this issue, can you change the label

@ThomasKranitsas
Copy link
Contributor

@RAJKUMARRRR please use this link https://x.topcoder.com/api/v1/github/teams/registration/7946e40e-f01a-4ced-a1c2-081e328c7d73-1553097709824 to access our org so you can assign yourself

@ThomasKranitsas
Copy link
Contributor

Contest https://www.topcoder.com/challenges/30086772 has been updated - it has been assigned to LieutenantRoger.

This is an automated message for thomaskranitsas via Topcoder X

@LieutenantRoger
Copy link
Collaborator

Hey @ThomasKranitsas ,

So when the password is incorrect, how do we notify the user ?

@ThomasKranitsas
Copy link
Contributor

Hey @LieutenantRoger ,

Please show an error like the one from the following screenshot:
Screenshot 2019-03-21 at 10 06 40

@ThomasKranitsas
Copy link
Contributor

The error can say The old password is invalid

@LieutenantRoger
Copy link
Collaborator

https://take.ms/skp6M

Can we show a tip like this ? To match the popup with the email invalid state on this same screen ?

@ThomasKranitsas
Copy link
Contributor

No, please use the one I shared above

@LieutenantRoger
Copy link
Collaborator

Ok, https://take.ms/XL8WY does this style look good to you ? I picked an existing one.

And this is only for client side validation, we won't check with backend about whether current password correct or wrong, right ? Because invalid only indicates a format error.

@ThomasKranitsas
Copy link
Contributor

I think there's a misunderstanding here... This error is shown when you submit the form and the backend returns an error.

It's not a form validation error, it's a bad request error

@LieutenantRoger
Copy link
Collaborator

Hey @ThomasKranitsas, I have read the backend codebase, it looks like the topcoder-react-lib didn't handle the error case when updating failed.

Can we use fireErrorMessage('The old password is invalid'); to notify user about the fail ? As I can see there are other errors in the topcoder-react-lib is using this way to alert error.

The way you showed above actually was a client validation style.

Let me know your thoughts.

@ThomasKranitsas
Copy link
Contributor

ThomasKranitsas commented Mar 21, 2019 via email

@LieutenantRoger
Copy link
Collaborator

ok, do I create a pull request on topcoder-react-lib master branch? I didn't find a bug-bash branch on that codebase.

@ThomasKranitsas
Copy link
Contributor

ThomasKranitsas commented Mar 21, 2019 via email

@LieutenantRoger
Copy link
Collaborator

LieutenantRoger commented Mar 21, 2019

When I modify the topcoder-react-lib in the community codebase's node_module folder, and re-build the community-app, do you know why the bundled topcoder-react-lib is not containing my update to the topcoder-react-lib ?

@ThomasKranitsas
Copy link
Contributor

You also need to build the topcoder-react-lib before you replace it in the community-app

@LieutenantRoger
Copy link
Collaborator

LieutenantRoger commented Mar 21, 2019

factory:45ms building:314ms = 359ms

ERROR in ./src/index.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
ReferenceError: [BABEL] /Users/Roger/w/bb/tc/topcoder-react-lib/src/index.js: Unknown option: base.envName. Check out http://babeljs.io/docs/usage/options/ for more information about options.

A common cause of this error is the presence of a configuration options object without the corresponding preset name. Example:

Invalid:
  `{ presets: [{option: value}] }`
Valid:
  `{ presets: [['presetName', {option: value}]] }`

For more detailed information on preset configuration, please see https://babeljs.io/docs/en/plugins#pluginpresets-options.
    at Logger.error (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/file/logger.js:41:11)
    at OptionManager.mergeOptions (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/file/options/option-manager.js:226:20)
    at OptionManager.init (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
    at File.initOptions (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/file/index.js:212:65)
    at new File (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/file/index.js:135:24)
    at Pipeline.transform (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transpile (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-loader/lib/index.js:50:20)
    at Object.module.exports (/Users/Roger/w/bb/tc/topcoder-react-lib/node_modules/babel-loader/lib/index.js:173:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build:dev: `webpack --env=development --progress --profile --colors --display-optimization-bailout`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] build:dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Roger/.npm/_logs/2019-03-21T16_07_08_072Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build: `npm run clean && npm run build:dev && npm run build:prod`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Roger/.npm/_logs/2019-03-21T16_07_08_106Z-debug.log

I can't build topcoder-react-lib both develop and master branch, can you see the issue ?

@LieutenantRoger
Copy link
Collaborator

@ThomasKranitsas
Please check this PR against topcoder-react-lib
Thanks.
topcoder-platform/topcoder-react-lib#48

@ThomasKranitsas
Copy link
Contributor

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30086772

This is an automated message for thomaskranitsas via Topcoder X

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

No branches or pull requests

4 participants