13 Commits (18a1d4c5c63bb8264dee15432e3c4d88d54d51b1)

Author	SHA1	Message	Date
ppoulard	02f14d967f	Fix stupid error 💥🗯💣🕳💢☠	7 years ago
ppoulard	49a89b80cf	Fix QA	7 years ago
ppoulard	ee81775dc8	Adding SSO CAS to Wekan	7 years ago
Ghassen Rjab	c0d33d97f2	Fix lint errors related to language names	7 years ago
Lauri Ojansivu	9d7ff75d3f	Fix Igbo language at menu.	7 years ago
Lauri Ojansivu	7e4b42e9b3	Fix: Frequent Subscriptions problem that make Excessive CPU usage. ... Thanks to mfshiu ! Closes #1096, Closes wekan/wekan-mongodb#2	8 years ago
Ghassen Rjab	80d73b9910	Add Breton label	8 years ago
Ghassen Rjab	a9dde296bf	Sort available languages by their translated names	8 years ago
lkisme	1dfb6ef477	Admin panel: ... Only invited user can register in strict mode, Set mail server in admin panel, Switch strict mode in admin panel, Invite people to system in admin panel	8 years ago
floatinghotpot	ec130d4480	add: use user preferred lang for user form, and allow selecting	10 years ago
Maxime Quandalle	b3851817ec	Enforce a consistent ES6 coding style ... Replace the old (and broken) jshint + jscsrc by eslint and configure it to support some of the ES6 features. The command `eslint` currently has one error which is a bug that was discovered by its static analysis and should be fixed (usage of a dead object).	10 years ago
Maxime Quandalle	9faaf07e02	Implement a modal system ... I decided to create my own and not to use a community package, because 1. it's straightforward 2. it's better integrated with our others libs such as EscapeActions 3. monitoring third-party packages evolutions (eg, CSS changes) is a lot of work. This is basically the same rationale than for our other generic UI components such as the Popup/Popover. This commit also slightly modify the general layout to remove unnecessary wrapper DOM nodes.	10 years ago
Maxime Quandalle	d5eec54c72	Start the migration from iron-router to flow-router ... Motivations: * Iron-Router foces us to use Tracker.nonreactive black magic in order to avoid un-necessary re-renders; * There is a community consensus (supported by some MDG members) that the flow-router API is easier to reason about; * The useraccounts now supports flow router (that was a blocking element when I considered the switch ~3months ago) On the server we use the Picker router, as encouraged by the Kadira team (which develop both Flow and Picker routers). In the current state of things there are some bugs related to the missing Loading architecure. Previously onRendered callback where always called when the data the component needed was available, now we have to handle this ourselves, which we will in a following commit.	10 years ago