Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Limit “copy from existing target gene” to the user’s own target genes. #307

Merged
merged 1 commit into from
Nov 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/components/screens/ScoreSetCreator.vue
Original file line number Diff line number Diff line change
Expand Up @@ -584,7 +584,7 @@
<div class="mavedb-wizard-help">
<label>Copy target from a previously created target</label>
<div class="mavedb-help-small">
Use this autocomplete field to find an existing target in MaveDB and fill this target with its metadata. You'll still be able to edit any fields below.
Use this autocomplete field to find an existing target from one of your published or unpublished score sets in MaveDB and fill this target with its metadata. You'll still be able to edit any fields below.
</div>
</div>
<div class="mavedb-wizard-content field">
Expand Down
2 changes: 1 addition & 1 deletion src/lib/item-types.js
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ const itemTypes = {
httpOptions: {
list: {
method: 'post',
url: `${config.apiBaseUrl}/target-genes/search`
url: `${config.apiBaseUrl}/me/target-genes/search`
Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps worth it to change the item type name too to be clear about being the users' own target genes when we construct the item?

}
}
},
Expand Down