In the root of your project, add .gitlab-ci.yml
with the configuration below.
image: node:latest
stages:
import SwiftUI | |
struct ContentView: View { | |
@State var show = false | |
var body: some View { | |
VStack { | |
Button("Pop Sheet") { show.toggle() } | |
} | |
.adaptiveSheet(isPresent: $show) { SheetView() } | |
} |
import SwiftUI | |
extension Calendar { | |
func generateDates( | |
inside interval: DateInterval, | |
matching components: DateComponents | |
) -> [Date] { | |
var dates: [Date] = [] | |
dates.append(interval.start) |
This is a walkthrough of how to set up Visual Regression Testing with Jest for an application created with create-react-app
.
The following walkthrough uses React as an example, but the approach should work for any modern frontend library! I assume it can be used with Angular, Vue, Cycle.js and more.
This gist walks you through a create-react-app
application as an example of how to set up Visual Regression Testing in Jest using libraries I wrote recently which enable this: jsdom-screenshot
, jest-transform-css
and jest-transform-file
.
import { Injectable } from '@angular/core'; | |
import { Observable, BehaviorSubject } from 'rxjs/Rx'; | |
@Injectable() | |
export class AudioService { | |
public audio: HTMLAudioElement; | |
public timeElapsed: BehaviorSubject<string> = new BehaviorSubject('00:00'); | |
public timeRemaining: BehaviorSubject<string> = new BehaviorSubject('-00:00'); | |
public percentElapsed: BehaviorSubject<number> = new BehaviorSubject(0); |
#!/bin/bash | |
alias npmrun='npm run' | |
alias _npmscripts_print="node -e \"console.log(Object.keys(require('./package.json').scripts, null, ' ').join(' '))\"" | |
_npmscripts_completion() | |
{ | |
local cur=${COMP_WORDS[COMP_CWORD]} | |
opts=$( _npmscripts_print ) | |
COMPREPLY=( $(compgen -W "${opts}" -- $cur) ) | |
} | |
complete -F _npmscripts_completion npmrun |
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message consists of a header, a body, and a footer.