| .. |
|
client-call-bidistreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
client-call-clientstreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
client-call-serverstreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
client-call-unary.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
client.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
main.swift
|
9ce9d6914e
Rename generated files to "<FILE>.rpc.swift".
|
8 years ago |
|
server-session-bidistreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
server-session-clientstreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
server-session-serverstreaming.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
server-session-unary.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
|
server.swift
|
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).
|
7 years ago |
Daniel Alm
2e00c363cc
Extract the interface of generated code for the `...Call`, `...Session` and `...Service` classes into protocols and make the implementing classes conform to those protocols. This lets us create custom implementations of those protocols, e.g. mocks/stubs/fakes/spies for testing purposes. In particular, this commit also includes an option to have simple fake implementations generated for the above protocols in addition to the "real" implementations (see #120 for a detailed discussion).