How to define dynamic interface/struct
I'm pretty new to Go and really looking for some guidance.
In my application I have a channel that receives events, I'd like to have an interface like:
{
"type": "event1",
"data": {}
}
where the structure of data depends on the type.
Then the code that listen for those events in the channel will know what kind of structure to expect based on the type of the event.
How can I define such interface?
Is that considered a good practice in Go?
Thanks in advance
go struct interface channel edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
add a comment |
I'm pretty new to Go and really looking for some guidance.
In my application I have a channel that receives events, I'd like to have an interface like:
{
"type": "event1",
"data": {}
}
where the structure of data depends on the type.
Then the code that listen for those events in the channel will know what kind of structure to expect based on the type of the event.
How can I define such interface?
Is that considered a good practice in Go?
Thanks in advance
go struct interface channel edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
add a comment |
I'm pretty new to Go and really looking for some guidance.
In my application I have a channel that receives events, I'd like to have an interface like:
{
"type": "event1",
"data": {}
}
where the structure of data depends on the type.
Then the code that listen for those events in the channel will know what kind of structure to expect based on the type of the event.
How can I define such interface?
Is that considered a good practice in Go?
Thanks in advance
go struct interface channel edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
I'm pretty new to Go and really looking for some guidance.
In my application I have a channel that receives events, I'd like to have an interface like:
{
"type": "event1",
"data": {}
}
where the structure of data depends on the type.
Then the code that listen for those events in the channel will know what kind of structure to expect based on the type of the event.
How can I define such interface?
Is that considered a good practice in Go?
Thanks in advance
go struct interface channel go struct interface channel edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
edited Nov 17 '18 at 18:30
Flimzy
37.4k96496
37.4k96496
asked Nov 16 '18 at 19:11
teone
88431436
asked Nov 16 '18 at 19:11
teone
88431436
asked Nov 16 '18 at 19:11
teone
88431436
88431436
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You are looking for a type switch:
package main
import (
"fmt"
)
type X struct {
i int
}
func main() {
c := make(chan interface{}, 5)
c <- 4
c <- "hi"
c <- X{}
close(c)
for value := range c {
switch v := value.(type) {
case int:
fmt.Println("got int", v)
case string:
fmt.Println("got string", v)
case X:
fmt.Println("got X", v)
default:
fmt.Printf("unexpected type %Tn", value)
}
}
}
answered Nov 16 '18 at 19:25
poy
6,40763364
Or just a normalswitchsince they already have astringfield that gives a type indicator.
– Adrian
Nov 16 '18 at 19:33
That's true, ifeventalways corresponds to the type of data, then that would be a simpler solution.
– poy
Nov 16 '18 at 19:57
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53344023%2fhow-to-define-dynamic-interface-struct%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You are looking for a type switch:
package main
import (
"fmt"
)
type X struct {
i int
}
func main() {
c := make(chan interface{}, 5)
c <- 4
c <- "hi"
c <- X{}
close(c)
for value := range c {
switch v := value.(type) {
case int:
fmt.Println("got int", v)
case string:
fmt.Println("got string", v)
case X:
fmt.Println("got X", v)
default:
fmt.Printf("unexpected type %Tn", value)
}
}
}
answered Nov 16 '18 at 19:25
poy
6,40763364
Or just a normalswitchsince they already have astringfield that gives a type indicator.
– Adrian
Nov 16 '18 at 19:33
That's true, ifeventalways corresponds to the type of data, then that would be a simpler solution.
– poy
Nov 16 '18 at 19:57
add a comment |
You are looking for a type switch:
package main
import (
"fmt"
)
type X struct {
i int
}
func main() {
c := make(chan interface{}, 5)
c <- 4
c <- "hi"
c <- X{}
close(c)
for value := range c {
switch v := value.(type) {
case int:
fmt.Println("got int", v)
case string:
fmt.Println("got string", v)
case X:
fmt.Println("got X", v)
default:
fmt.Printf("unexpected type %Tn", value)
}
}
}
answered Nov 16 '18 at 19:25
poy
6,40763364
Or just a normalswitchsince they already have astringfield that gives a type indicator.
– Adrian
Nov 16 '18 at 19:33
That's true, ifeventalways corresponds to the type of data, then that would be a simpler solution.
– poy
Nov 16 '18 at 19:57
add a comment |
You are looking for a type switch:
package main
import (
"fmt"
)
type X struct {
i int
}
func main() {
c := make(chan interface{}, 5)
c <- 4
c <- "hi"
c <- X{}
close(c)
for value := range c {
switch v := value.(type) {
case int:
fmt.Println("got int", v)
case string:
fmt.Println("got string", v)
case X:
fmt.Println("got X", v)
default:
fmt.Printf("unexpected type %Tn", value)
}
}
}
answered Nov 16 '18 at 19:25
poy
6,40763364
You are looking for a type switch:
package main
import (
"fmt"
)
type X struct {
i int
}
func main() {
c := make(chan interface{}, 5)
c <- 4
c <- "hi"
c <- X{}
close(c)
for value := range c {
switch v := value.(type) {
case int:
fmt.Println("got int", v)
case string:
fmt.Println("got string", v)
case X:
fmt.Println("got X", v)
default:
fmt.Printf("unexpected type %Tn", value)
}
}
}
answered Nov 16 '18 at 19:25
poy
6,40763364
answered Nov 16 '18 at 19:25
poy
6,40763364
answered Nov 16 '18 at 19:25
poy
6,40763364
answered Nov 16 '18 at 19:25
poy
6,40763364
6,40763364
Or just a normalswitchsince they already have astringfield that gives a type indicator.
– Adrian
Nov 16 '18 at 19:33
That's true, ifeventalways corresponds to the type of data, then that would be a simpler solution.
– poy
Nov 16 '18 at 19:57
add a comment |
Or just a normalswitchsince they already have astringfield that gives a type indicator.
– Adrian
Nov 16 '18 at 19:33
That's true, ifeventalways corresponds to the type of data, then that would be a simpler solution.
– poy
Nov 16 '18 at 19:57
Or just a normal
switch since they already have a string field that gives a type indicator.– Adrian
Nov 16 '18 at 19:33
Or just a normal
switch since they already have a string field that gives a type indicator.– Adrian
Nov 16 '18 at 19:33
That's true, if
event always corresponds to the type of data, then that would be a simpler solution.– poy
Nov 16 '18 at 19:57
That's true, if
event always corresponds to the type of data, then that would be a simpler solution.– poy
Nov 16 '18 at 19:57
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53344023%2fhow-to-define-dynamic-interface-struct%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
