Pierre de La Morinerie fc8a0d46ff editor: insert new champs after the last fully visible champ ... Before, when the "Add new champ" button was clicked, the new champ was inserted after the **first** fully visible champ. That was most of the time unexpected. The correct behavior would be to insert the new champ after the **last** fully visible champ. That's what this commit does. Now the "Add new champ" behavior feels much less confusing.		2019-11-07 15:19:11 +01:00
..
assets	RGAA fix : 9.1.2 Dans chaque page Web, la hiérarchie entre les titres (balises h ou balise possédant un role ARIA "heading" associé à une propriété aria-level) est-elle pertinente ?	2019-11-06 17:01:07 +01:00
controllers	Guard for missing attestation on dossier	2019-11-06 12:54:07 +01:00
dashboards	Rename gestionnaire in code to instructeur	2019-08-12 13:47:01 +02:00
fields	manager: remove support for old pj	2019-07-30 16:11:17 +02:00
graphql	[GraphQL] Add create direct upload mutation	2019-11-07 12:48:51 +01:00
helpers	Make (part of) the html valid again	2019-11-06 17:01:07 +01:00
javascript	editor: insert new champs after the last fully visible champ	2019-11-07 15:19:11 +01:00
jobs	cleanup the queue flag during cleanup job	2019-10-24 16:27:10 +02:00
lib	[API Carto]: use typhoeus and correctly handle errors	2019-11-06 11:10:56 +01:00
mailers	add explanation about rescue_from in application_mailer	2019-11-07 10:13:11 +01:00
models	Handle non unique champ repetable labels	2019-11-07 14:27:52 +01:00
policies	champ_policy: allow instructeurs to access private annotations	2019-10-08 14:34:12 +02:00
serializers	instructeurs: alias instructeur.email	2019-11-04 10:44:24 +01:00
services	Handle non unique champ repetable labels	2019-11-07 14:27:52 +01:00
validators	gestion des 2 formats de bouton monavis	2019-09-17 13:39:45 +02:00
views	Follow flipper name convention to appears on manager admin page	2019-11-07 11:09:05 +01:00