This post described how to create an application with mithril 0.2.x. Now that ver 1.0 is out, some things are a little differnent.
The example is updated with the current version of mithril, though.
| var url = require('url'); | |
| var crypto = require('crypto'); | |
| /* | |
| NTLM PROCESS FOR GET REQUESTS: | |
| ============================== | |
| STEP 1: The Client requests a protected resource from the server | |
| STEP 2: The Server responds with a 401 status, with a header indicating that the client must authenticate | |
| STEP 3: The Client resubmits the request with an Authorization header containing a Base-64 encoded Type 1 message. From this point forward, the connection is kept open; closing the connection requires reauthentication of subsequent requests. | 
| /** | |
| * ``` | |
| * Does JDK8's Optional class satisfy the Monad laws? | |
| * ================================================= | |
| * 1. Left identity: true | |
| * 2. Right identity: true | |
| * 3. Associativity: true | |
| * | |
| * Yes, it does. | |
| * ``` | 
This post described how to create an application with mithril 0.2.x. Now that ver 1.0 is out, some things are a little differnent.
The example is updated with the current version of mithril, though.
| // | |
| // ContentView.swift | |
| // AnimationTimingCurve | |
| // | |
| // Created by Chris Eidhof on 25.09.19. | |
| // Copyright © 2019 Chris Eidhof. All rights reserved. | |
| // | |
| import SwiftUI | 
| @Configuration | |
| public class BeanValidationConfig { | |
| /** | |
| * The idea here is to configure Hibernate to use the same ValidatorFactory used by Spring, | |
| * so that Hibernate will be able to handle custom validations that need to use dependency injection (DI) | |
| */ | |
| @Bean | |
| public HibernatePropertiesCustomizer hibernatePropertiesCustomizer(final Validator validator) { | |
| return new HibernatePropertiesCustomizer() { |