Age | Commit message (Collapse) | Author |
|
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
|
|
|
|
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
|
|
* wqflask/wqflask/templates/generif.html: New template.
* wqflask/wqflask/views.py (display_diffs_users): New route.
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
|
|
At this point, the code fails with a 404, despite the appropriate
endpoint existing. Will need further debugging.
|
|
This reverts commit b8b62aea1c7924e2ee7455c6fe8b34eee7cb8e74.
We do need to decouple the entire `gn3.db_utils` from the
`flask.current_app` object, and as such, the use of `SQL_URI` from the
`utility.tools` module in GN2 was on purpose. This is also to help
towards fixing issue
https://issues.genenetwork.org/issues/bugfix_coupling_current_app_and_db_utils
|
|
|
|
|
|
|
|
|
|
This was just caused by the correlation code not directly being passed the PMID (and instead only being passed the link and the text), so the logic in the table code needed to be changed to check for the link instead of the PMID
|
|
I think it now gets the SQL_URI from settings
|
|
|
|
|
|
|
|
Enable search when user types in search box. Filter out any selected
datasets.
|
|
|
|
Move the javascript to an external file to ease development.
Generalise some functions to make it easier to reuse the code down the line.
|
|
|
|
Genenetwork2 configs are a tad weird, and instead of using the configs
in `flask.current_app`, we need to use those in `utility.tools`.
|
|
|
|
Remove use of deprecated function and fix a myriad of bugs that rise
from its removal.
Issue: https://issues.genenetwork.org/issues/bugfix_coupling_current_app_and_db_utils
|
|
When a user selects a dataset in the search table, automatically add
it to the link table and remove it from the search table.
|
|
Simplify the implementation by dropping the use of the jQuery
DataTables plugin - this avoids a lot of arising bugs while retaining
the UI look and feel until we have something working.
|
|
Try auto-selecting datasets on user click: not successful at this
point.
There are some weird bugs with the DataTables that I have not been
able to resolve yet.
|
|
Since the table data could change depending on user input, save the
state in the `data-*` attributes to enable update of tables on
changes.
|
|
|
|
|
|
|
|
|
|
|
|
Filter out data as the user types, with a short delay to prevent
searching on each and every character.
|
|
Provide a UI for the phenotype datasets with a search
interface (currently inactive) that is eventually going to allow for
linking the traits to user groups.
|
|
|
|
The previous code caused an error when the mean was N/A (when trying to
take the float() of it)
|
|
|
|
|
|
* wqflask/wqflask/metadata_edits.py (update_phenotype): Add url to
diff page in flash message.
* wqflask/wqflask/templates/edit_phenotype.html: Render flash message
with HTML.
|
|
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
|
|
ATM, editing case-attributes is very buggy.
* wqflask/tests/integration/wqflask/test_metadata_edits.py: Delete.
* wqflask/wqflask/decorators.py: Remove:
gn3.authentication.get_groups_by_user_uid import.
(case_attributes_edit_access): Delete.
* wqflask/tests/integration/wqflask/test_metadata_edits.py: Remove
wqflask.decorators.case_attributes_edit_access,
gn3.db.case_attributes.get_case_attributes,
gn3.db.case_attributes.get_unreviewed_diffs,
gn3.db.case_attributes.insert_case_attribute_audit,
gn3.db.case_attributes.reject_case_attribute and
gn3.db.case_attributes.approve_case_attribute.
(display_phenotype_metadata): Remove headers arg when rendering
template.
(update_phenotype): Remove case attribute headers list when updating a
phenotype.
(show_case_attribute_columns, update_case_attributes): Delete.
(reject_case_attribute_data, approve_case_attribute_data): Ditto.
* wqflask/wqflask/templates/edit_phenotype.html: Remove link that
shows all the listed case-attributes.
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
|
|
In order to enable searching through the existing datasets for linking
with the auth system, we need a way to filter the data.
In this commit, I load the menu and load it onto a dropdown box as a
proof of concept to give an idea of some of the filters I can use down
the road to fetch the data.
This commit breaks the data-linking code. I will need to rework the
data-linking code entirely to get it working again.
|
|
|
|
List/link the phenotypes at the trait level rather than at the dataset level.
|
|
In the case that the JSON output from the correlations computation is
malformed, we capture that into a new exception an re-raise it to help
with debugging and fixing issues.
|
|
|
|
|
|
|
|
|
|
|
|
Edit Sample Data and Edit Metadata are now two separate sections, and Edit Sample Data appears first
|