-
Notifications
You must be signed in to change notification settings - Fork 1
Transformation Workflow #290
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -61,7 +61,6 @@ export const Activities = { | |
| objectTypesToList: [ | ||
| ObjectTypes.Plasmids.id, | ||
| ObjectTypes.Strains.id, | ||
| ObjectTypes.Assembly.id, | ||
| ObjectTypes.Transformations.id, | ||
| ] | ||
|
Comment on lines
61
to
65
|
||
| }, | ||
|
|
||
This file was deleted.
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.
Dropping
ObjectTypes.Assembly.idfrom the Build activity removes the only explorer bucket that can surface existing assembly-plan assets, but the app still classifies OneDrive files underassemblyPlans/*.jsonassynbio.object-type.assembly-plan(mapOneDriveItemToObjectTypeinfrontend/src/microsoft-utils/oneDrive/fetchFromOneDrive.js). After this change, users with pre-existing assembly plans can no longer find/open those files from the workflow UI, which is a regression in data accessibility unless a migration/fallback path is added.Useful? React with 👍 / 👎.