Age | Commit message (Collapse) | Author |
|
|
|
require leap_ca from leap_web_certs to ensure consistency
|
|
|
|
Client-side validations, including only validating email address format ...
|
|
|
|
moving the js for view definitions into separate files
|
|
|
|
|
|
|
|
|
|
something is input for email address.
|
|
it) of user who created ticket.
|
|
|
|
This way we get syntax highlighting and so on.
|
|
validating email domain and displaying it as the placeholder
|
|
Use two config files - one for defaults that is always present and one to overwrite these
|
|
|
|
Only non-comment change is that we will keep an unauthenticated user looking at the same ticket if they have closed it (rather than redirecting to index which they will not be able to access.)
|
|
the order either way.
|
|
|
|
|
|
feature/validate-email-domain
|
|
|
|
This even works client side. :)
|
|
|
|
You can overwrite them in config/config.yml
|
|
|
|
Removing email aliases - proper error display
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
using CouchRests user.email_aliases.build so the casted_by method is set in the alias
Used this to move the validations into the alias itself. This is where they belong and allows us to render the errors inline along the email field they belong to.
|
|
Actually that might not be the best idea.
Issue at hand was that invalid email aliases were getting displayed when rendering the edit form again. We probably want to solve this different.
|
|
still needs a bit of refactoring in the view
|
|
|
|
|
|
https://github.com/leapcode/leap_web
|
|
Adopt certs to changes in the leap ca
|
|
|
|
|
|
|
|
|
|
|
|
fixes #1168
[ci skip]
|
|
[ci skip]
|