-
Notifications
You must be signed in to change notification settings - Fork 82
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
Share UI Submit fix #1403
Share UI Submit fix #1403
Conversation
const handlePageChange = async (event, value) => { | ||
if (value <= sharedItems.pages && value !== sharedItems.page) { | ||
await setFilter({ ...filter, page: value }); | ||
} | ||
}; | ||
|
||
const beforeClose = async () => { | ||
if (smthChanged || requestPurpose !== share.requestPurpose) { | ||
if (requestPurpose !== share.requestPurpose) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to add setSmthChanged(true);
for if no response errors for updateRequestPurpose
then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updateRequestPurpose doesn't change the state of Share. So, basically, there is nothing to submit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@noah-paige may be we should change that, but not before 2.6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
onApply
just refreshed the ShareObject and associated share items in the view right?
If we do not run onApply()
then I can update the request purpose --> hit Save & Close
--> the share view is not updated and the old request purpose still shows
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, yes, you are right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Feature or Bugfix
Detail
Relates
Security
Please answer the questions below briefly where applicable, or write
N/A
. Based onOWASP 10.
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
eval
or similar functions are used?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.