| Age | Commit message (Collapse) | Author |
|---|
|
This needs to be included in the platforms views.
|
|
|
|
|
|
|
|
This is an initial draft of the keys api for uploading other
keys than the OpenPGP public key.
refers #8815
|
|
ci: also test with ruby 2.4
Closes #8812
See merge request leap/webapp!56
|
|
|
|
Upgrade/gemfile
See merge request leap/webapp!55
|
|
|
|
|
|
|
|
* on invalid key upload respond with error and 422 response code
* fix alternate email address dialogue
* publish public key in webfinger
* update translations from transifex
* hand out config.json without auth
* sanity checks on user params
* cleanup temp invites from server tests so they do not clutter admin ui
|
|
Fix/8798 key errors
Closes #8798
See merge request leap/webapp!54
|
|
We used to just ignore the key.
Also separated the code for handling key updates from other
user updates. This should eventually be moved to a different
route. Mixing the two makes the implementation really hard.
|
|
also ensures that created user is cleaned up even if test fails
|
|
fix: alternate email dialogue
Closes #8796
See merge request leap/webapp!53
|
|
fixes #8796
Cleaned up UserController#update earlier but missed that it was
used to change fallback email addresses. Now it is back. This
time including an integration test.
|
|
fix #8010 - publish public key in webfinger
Closes #8010
See merge request leap/webapp!52
|
|
we were simply referring to the wrong key.
includes test
|
|
i18n: update translations from transifex
Closes #8797
See merge request leap/webapp!51
|
|
|
|
feat: allow unauthenticated access to list of configs
Closes #8800
See merge request leap/webapp!45
|
|
fix: sanity checks on user params
Closes #8801
See merge request leap/webapp!50
|
|
fixes #8801
Includes a test reproducing 500 on lynx
We now make use of ActionController::Parameters require and permit
methods.
|
|
Bugfix/8807 cleanup tmp invites
Closes #8807
See merge request leap/webapp!49
|
|
This simplifies returning the user while still working
on it a lot. Much cleaner than all these return user statements.
There's a lot more to refactor here. For example delegating methods
to user etc. ... but for now this should suffice. Don't want to
break this in a bugfix release.
|
|
fixes #8807
|
|
Bugfix release for 0.9:
* pin to the newest psych gem
* remove better_errors gem
* fix login error message with non en locales
Features:
* destroy invites used to create test accounts
* sort invite codes by last update
|
|
feat: sort invite codes by last update
Closes #8806
See merge request leap/webapp!48
|
|
They used to be sorted by the code which was not helpful
fixes #8806
requires deploy of new design docs to the platform
|
|
fix: destroy invites used to create test accounts
See merge request leap/webapp!47
|
|
Production instances are getting cluttered with invites from
test accounts. Instead of marking them as used we will now completely
remove them.
refers to #8804
refers to #8807\
|
|
fix: login error message with locale set
Closes #8805
See merge request leap/webapp!46
|
|
On a failed login the warden failure app gets called.
Some of the params are changed accordingly but controller
and action remain.
set_locale would detect there was no locale in the path
and thus attempt to redirect. However the params still
belong to the previous request which was a POST to
Api::SessionsController.
This route does not respond to get requests and so it
would trigger a 404 in production and a 500 in development.
This commit prevents set_locale to act upon warden failure
app controller calls by adding /new to the list of
`NON_LOCALE_PATHS`. (The path is updated by warden to the
name of the action called in the failure app).
A test is included in this commit that tries to login
with an invalid username, password combination and a german
locale set.
fixes #8805
|
|
This should simplify client code significantly according to
platform#8849
|
|
|
|
pin to the newest psych gem, so as to not hit bugs in older versions (required by faker)
See merge request !44
|
|
it is currently incompatible with haml
|
|
|
|
|
|
(required by faker)
|
|
Plain bugfix release for 0.9:
* prevent token conflicts
* custom: fix stylesheet customization
* fix: set token in forms correctly
|
|
|
|
prevent token conflicts
Closes #8792
See merge request !42
|
|
|
|
Fix/sass load path
Closes #8794
See merge request !40
|
|
fixes #8794
Reported the underlying issue here:
https://github.com/rails/sass-rails/issues/406
Basically `@import` works like this:
* look for the file relative to the current file
* look for the file as an absolute path following the priorities in the
* asset load_paths
If the file can be imported as a relative path that will take
precedence.
So in order to pick up the head and tails inside customization rather
than in app/assets there are three possibilities:
1) use an absolute path. This is not as easy as it seems. There is no
way of indicating a path is meant to be absolute so we would have to
ensure it does not resolve to a relative path.
2) have a application.scss file inside the customization folder. Since
this is the main file it will be used instead of the app/assets one. In
there relative paths will now also default to the customization folder
rather than app/assets. Once we are in an app/assets file though it will
not go back to picking up customization with relative paths
3) use //= require instead of import. rails-sass advices against this as
each required file would be compiled on it's own and variables could not
be shared.
Going with option 1 here:
```scss
// application.scss:
@import "custom/head_import";
```
```scss
// custom/head_import.scss:
@import "head";
```
As long as there is no custom/head.scss in app/assets it will import
head as an absolute path and thus prefer config/custom over app/assets.
This seems like the best option for now as it does not require changes
to the deployments.
|
|
This reverts commit cc95bb27e873dc6140f9a909a57f075a0ef2f387.
|
|
fix: make customization available to sass
Closes #8793
See merge request !39
|
|
Somehow sass did not follow the rails assets path order.
Therefore the default tail.scss would stay in effect even when
there was a different tail.scss in the customization folder.
Adding the customization stylesheet folder to the sass load_paths
works around this for now. Still need to check if it works in
production though.
|
