| package com.google.firebase.zerotoapp; | |
| public class ChatMessage { | |
| public String name; | |
| public String message; | |
| public ChatMessage() { | |
| } | |
| public ChatMessage(String name, String message) { |
| <html> | |
| <head> | |
| <script src="https://www.gstatic.com/firebasejs/3.0.0/firebase.js"></script> | |
| <title>ZeroToApp</title> | |
| <style> | |
| #messages { width: 40em; border: 1px solid grey; min-height: 20em; } | |
| #messages img { max-width: 240px; max-height: 160px; display: block; } | |
| #header { position: fixed; top: 0; background-color: white; } | |
| .push { margin-bottom: 2em; } | |
| @keyframes yellow-fade { 0% {background: #f2f2b8;} 100% {background: none;} } |
| /* | |
| This example shows how you can use your data structure as a basis for | |
| your Firebase security rules to implement role-based security. We store | |
| each user by their Twitter uid, and use the following simplistic approach | |
| for user roles: | |
| 0 - GUEST | |
| 10 - USER | |
| 20 - MODERATOR |
| import {Injectable} from '@angular/core'; | |
| import {FirebaseAuth, AngularFire} from "angularfire2"; | |
| import {Subject, Observable, BehaviorSubject} from "rxjs"; | |
| import {AuthInfo} from "./auth-info"; | |
| @Injectable() | |
| export class AuthService { | |
| static UNKNOWN_USER = new AuthInfo(null); | |
| authInfo$: BehaviorSubject<AuthInfo> = new BehaviorSubject<AuthInfo>(AuthService.UNKNOWN_USER); |
| package main | |
| import ( | |
| "crypto/aes" | |
| "crypto/cipher" | |
| "crypto/rand" | |
| "encoding/base64" | |
| "fmt" | |
| "io" | |
| ) |
| #!/bin/bash | |
| go test -coverprofile=coverage.out | |
| go tool cover -html=coverage.out |
| package main | |
| import ( | |
| "fmt" | |
| "io" | |
| "os" | |
| ) | |
| var path = "/Users/novalagung/Documents/temp/test.txt" |
| language: go | |
| # Only the last two Go releases are supported by the Go team with security | |
| # updates. Any versions older than that should be considered deprecated. | |
| # Don't bother testing with them. tip builds your code with the latest | |
| # development version of Go. This can warn you that your code will break | |
| # in the next version of Go. Don't worry! Later we declare that test runs | |
| # are allowed to fail on Go tip. | |
| go: | |
| - 1.7 |
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the AngularJS change log.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE hibernate-configuration PUBLIC | |
| "-//Hibernate/Hibernate Configuration DTD 3.0//EN" | |
| "http://hibernate.org/dtd/hibernate-configuration-3.0.dtd"> | |
| <hibernate-configuration> | |
| <session-factory> | |
| <property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property> | |
| <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/Book</property> | |
| <property name="hibernate.connection.username">root</property> | |
| <property name="hibernate.connection.password"></property> |