UI configuration and additions #380
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # webtool/templates/components/result-details.html # webtool/views/views_dataset.py
Is this a good way to do it? 🤔
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows admins to configure more aspects of the 4CAT interface, including visibility of various result page components, and whether to preview mappable datasets as the mapped CSV or the underlying JSON.
Additionally, adds functionality that allows setting a 'default' configuration tag by passing a certain HTTP reader with the request.
Among other things, this should make it easier to configure 4CAT as a 'single data source' tool and offer multiple distinct front-end views via the same Flask/WSGI process.