-
Notifications
You must be signed in to change notification settings - Fork 16
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
Capacité à uploader un fichier pour les configurations #45
Labels
Comments
PonteIneptique
added a commit
that referenced
this issue
Mar 27, 2018
Jean-Baptiste-Camps
pushed a commit
that referenced
this issue
Apr 6, 2018
* Fixed issue #44 : Added bold. Warning : This change is breaking the former data model * Removed flask migrate remnants * Actually fixes issue #45 as well : moving to a proper click system * Added tests for scripts * Starting to implement client for importing data from CLI * Working test builder * Added export capacities * Extracted corpus input conversion to avoid code duplication * Added tests for the whole set of commands including corpus-list and corpus-dump * Moved corpus-import to corpus-from-file Created corpus-from-dir to easily reimport previous dump Not tested the last one * Finalizing wonderful at runtime generated tests for corpus-from-dir tests * Nice link * Quick link to last edit page
There is a very simple yet working (I think) implementation of this in the following branch : a129625 |
We estimate this ticket to take us 2d. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Idées
L'upload de fichier vers le serveur semble complètement inutile et pourrait provoquer une surchage à gérer. Par contre, on peut utiliser jQuery/Javascript pour lire le contenu d'un fichier et remplir les textarea :)
Ressources :
Actual behaviour
First situation
#tokens
and#allowed_lemma
,#allowed_POS
and#allowed_morph
need to received huge amount of data, most of the time they are copy pastedSecond situation
Expected Behaviour
Add a button so that
The text was updated successfully, but these errors were encountered: