Skip to content

Conversation

@akolson
Copy link
Member

@akolson akolson commented Jul 5, 2023

Summary

Description of the change(s) you made

This pr Prevent "Source" fields edits for copied/imported resources. Also please see this comment for context on fix made

Manual verification steps performed

Please see issues #3111 and #4090.

Does this introduce any tech-debt items?

No


Reviewer guidance

How can a reviewer test these changes?

  1. Create a channel A and channel B.
  2. Upload a file in channel A and then import the same file in channel B.
  3. Edit all details of the file in channel B.
  4. You should not be able to edit any of the fields under the "Source" section of the edit form.

References

Fixes #3111 and #4090

Comments


Contributor's Checklist

PR process:

  • If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
  • If this includes an internal dependency change, a link to the diff is provided
  • The docs label has been added if this introduces a change that needs to be updated in the user docs?
  • If any Python requirements have changed, the updated requirements.txt files also included in this PR
  • Opportunities for using Google Analytics here are noted
  • Migrations are safe for a large db

Studio-specifc:

  • All user-facing strings are translated properly
  • The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
  • All UI components are LTR and RTL compliant
  • Views are organized into pages, components, and layouts directories as described in the docs
  • Users' storage used is recalculated properly on any changes to main tree files
  • If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

  • Code is clean and well-commented
  • Contributor has fully tested the PR manually
  • If there are any front-end changes, before/after screenshots are included
  • Critical user journeys are covered by Gherkin stories
  • Any new interactions have been added to the QA Sheet
  • Critical and brittle code paths are covered by unit tests

Reviewer's Checklist

This section is for reviewers to fill out.

  • Automated test coverage is satisfactory
  • PR is fully functional
  • PR has been tested for accessibility regressions
  • External dependency files were updated if necessary (yarn and pip)
  • Documentation is updated
  • Contributor is in AUTHORS.md

Copy link
Member

@bjester bjester left a comment

Choose a reason for hiding this comment

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

The fixes definitely prevent editing, but I think more can be done to visually clarify their readonly state. Right now they don't look any different. This is actually the reason I mentioned disabled. Perhaps we want both?

Screenshot from 2023-07-06 13-09-42

@akolson
Copy link
Member Author

akolson commented Jul 8, 2023

Both seem to work as expected. It just seems overkill for me as a think disabled is sufficient.

@akolson
Copy link
Member Author

akolson commented Jul 8, 2023

disabled by itself also prevents interaction with those fields which I like but also backs your suggestion to use it. Thanks

'#'=0
'$'=7983
'*'=(  )
-=569JNRXghikls
'?'=127
@=(  )
ARGC=0
EPOCHREALTIME
EPOCHSECONDS
HISTCMD=5996
LINENO=24
PPID=76126
TTYIDLE=0
ZSH_EVAL_CONTEXT=toplevel:cmdsubst
ZSH_SUBSHELL=1
builtins
dis_builtins
dis_functions_source
dis_patchars
dis_reswords
epochtime
funcfiletrace
funcsourcetrace
funcstack
functions_source
functrace
history
historywords
jobdirs
jobstates
jobtexts
modules
parameters
patchars
reswords
status=127
terminfo
userdirs
usergroups
zsh_eval_context=( toplevel cmdsubst )
@akolson akolson requested a review from bjester July 8, 2023 17:30
Copy link
Member

@bjester bjester left a comment

Choose a reason for hiding this comment

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

LGTM

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants