AsyncAPI Community, 4 Feb 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: AsyncAPI SIG meeting 16 (Feb 4, 2020)

Description

This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #16.

Attendees:

- Fran Méndez
- Łukasz Gornicki
- Michael Davis

Moderation:
- Fran Méndez

Agenda:
- Channel deprecation (Fran)
- Generator templates parameters (Fran)
- Contribution workflow (Łukasz)
- Website publishing automation (Łukasz)

Chat dump:

18:05:56 From Fran Méndez : https://github.com/asyncapi/asyncapi/issues/304
18:08:00 From Fran Méndez : …
18:08:02 From Fran Méndez : https://github.com/asyncapi/asyncapi/issues/305

A

A

Meeting notes, you have to scroll to see the last comment and we were. We were discussing whether it's a good idea to have a channel deprecation flag or feature and listen KPIs, that you can mark that channel is deprecated, but then it went. It went farther a little bit farther as like a what about not just knowing. If something is implicated or not like it's, not a boolean right, I want to know more I want to know the reasons I want to know until or or I want you to warn me before.

A

It's deprecated right like this is gonna, be operating and still this date and time right so yeah, something like this and if, if it's there, an alternative channel so as a consumer, for instance, I would like to understand if okay, this channel is deprecated, but it's been a big deprecated soon. For this and other reasons and but I need this information. Where can I subscribe to get the same information or the same kind of information?

A

So yeah there are some. Let me there are some issues with this, so I mentioned specifically some people from the API community, because I know this. This conversation has been going on also on the on open API, so I think we can probably learn from their discussions. So we don't repeat the same things and let me try to find eyes here.

A

Let me share the link here: let's separate them there, so that's the issue, and so you can see that field sergeant. There left a huge comment: I hate, you feel if you're looking at this you're watching this yeah, it's great that you so the thing with this is it's always the same. Are we over engineering at the defecation feature? Are we getting not getting enough body of it out of it like, for instance, for me to forget it true or false? It seems like very little value.

A

Let me share my screen here so.

A

For me, something like deprecated truth is it's not very valuable? It is, but not so much and as Phil was explaining here, then that's the what the story, the discussion they had in the past, then they they thought. Okay, we can probably put a string here and it means it's duplicated and that's the reason why it is something as appertaining in our case is a channel. Then someone thought okay. So this is a message, and this is the alternative channel for us and but then people stepped up.

A

Instead, the saying like a what about scenes at versions hints, it gets more complex, encompasses I got so yeah I mean honestly I, don't have a I I have a gut feeling right that probably the last one is to over-engineered. So this is too much. Probably and I have the feeling that deprecated through is or deprecated with the messages. It's not enough. We could do better right and so probably having something like this or having something like I proposed.

A

Fear, like I, would I called this sunset by the way following the Heather definition, the HTTP header definition by edit filter, so so yeah, that's a by the way that says stunner. So we could probably follow the same more or less the same structure right so daytime the message: stop it now, an alternative channel I. Think the money, in my opinion, I, think that makes sense that will cover most of the use cases and then, as for instance, for for for feel, you said: they're deprecated through his wife.

A

Okay, that's you know as a matter of flavors right.

A

So I don't know, I wanted to know your opinion and this. What? What do you think is the best.

B

B

C

The date field is at the date that it's marked for removal like the cutoff date, or is it the date that it was marked as deprecated like in the previous example that you gave the sunset one, this one yeah you had one where you use sunset right, yeah, my ear suggestion yeah. So that daytime is that the date when it was introduced when when it was marked as deprecated or the day when it's gonna stop working. It's just.

B

A

C

Okay, yeah that that's that's useful, I yeah yeah I, think that's that's good. I mean to me. The message would probably you know could be like a link to an issue in JIRA or something like that. It explains more detail. I think you know, because I think that deprecating a channel is kind of probably a big deal in a lot of organizations, and you know different organizations might have different needs in terms of how much how much information do two people need, but yeah I could have something like that external dogs.

A

We already have it.

A

Open API, spec yeah, that's something we could have something like sterile dogs or external link.

A

So we could have I, don't know my.

A

C

A

No, so that that will because if we put it in a message, then, if we want to extract message from volume from the message, then we will have to parse it, and then it's you know it's human. It could be Spanish, it would be polish, it could be English, it could be anything like Chinese or whatever. So the message will then be structure them in any way right.

A

It should be just freeform information for the user, but if we want to have to have more information, I think that's welcome having an external link, which is also also optional right. In the end, the only the only required thing is to take time like just tell me when this is gonna, stop working and- and if you don't know when this is gonna, stop working. Just just put a I. Don't know five years from now something or ten years from now and forget.

C

About it, maybe it maybe it shouldn't be required. If, if you really don't know, I think it's better to to say if you're not sure exactly when and it's better to say that instead of making up you know incorrect information, but.

A

Then we have the problem of everything becoming optional. Then you can have an empty sunset object, yeah right, because if it's I mean if it's sunset, it's one thing: if it's deprecated is something different right, because actually deprecated means that it already happen. Right is in the past.

A

C

Not sure like not in well I mean I, see that word a lot in the Java world where certain classes and api's are marked as deprecated, but they still tend to work for you know years. They say well we're going to remove this in some later version, so you should move away from it, but there have been classes in the Java library that have been marked as deprecated for four years and several versions and they're still there so yeah I'm, not sure about that.

A

Yeah, it's just sometimes you sometimes you don't know where you're gonna said you're gonna remove complete, there's something. That's gonna stop working right, yeah yeah, it may be in the mid, be good to have. This is optional, as you said, then it's probably a matter of understanding.

A

Reworking the the solution, probably or probably I mean because deprecating and sunsetting have two different things right. So probably we could have something like this true or false right and when is something going to, we can be in sunset right when it's gonna be closed and stopped working like deprecated through deprecated could be true or false, and then sunset could just I.

A

Don't know the sunset could be just like when this is gonna stop working, because it's not gonna be deprecated anymore. It's actually because deprecated is something that's still there, but who don't use sunset? It's actually that when it's, when something is sunset, it mean that it's not gonna, be there anymore. It's like never existed right, it's gonna fail if you use it or if you try to use it right so yeah. So probably we're talking about two different things here: deprecation in Sun setting yeah.

C

Well, that vacation is kind of a warning that at some point it's gonna get sunsetted right. So, yes, okay, I'm, not I'm, not sure if they should be different, really I think definitely we need to think more about this I think.

A

Okay, okay, because I think this is this is important, because this this conversation already popped out popped up many times when talking to companies using a single API and or not using using API. But they are concerned about how to document the event driven attitude.

C

A

D

The link to that they sent the issue to the slack. Is there some more details? Like the use case, I mean how somebody would use it? Is it.

E

D

Just letting know the user that the following channel is deprecated and just that's it or yeah.

A

So, for instance, it's very common that versioning in event-driven architectures happen by changing the chain, the name of the check. So, for instance, like me, this.

A

You didn't see my notes for the kyouko presentation.

A

So something that happens many times is that you have something like this one, so that users.

A

Users has one created that could be like users, creative and and then you publish messages there. Every time my user has been created or something right, that's pretty common. But then at some point you have to make a breaking change on the message there and you shouldn't, but sometimes it's inevitable or it's cheaper. Then then trying to maintain everything backward-compatible.

A

So someone comes up with something like.

B

A

You shouldn't do this, but that's for an illustration purposes. So then, for instance, here you have imagine that here you have full name email and here you have.

A

First name last name: email.

A

That you could do, of course, is it. You can add first name here and last name, so you make.

A

But then you add to an existing message, and this keeps drawing over today. I'm gonna say some point. You have to stop doing this right or at the point you want to remove this anymore or something else like one.

A

So at some point you want to say this: this topic here is gonna, be removed completely removed, so you will not be able to subscribe to it.

A

2020, whatever right, that's the that's the thing, so you you're hinting people using your service or subscribing to your topic or whatever you're hinting people that they should start migrating to this other topic, which will contain the same information conceptually, but in a different way. You will have to change your code right, you'll have to change instead of receiving full name. You will receive this and you will have to join both and you know what I mean. So that's that's. It come on use case, let's say and.

D

The idea is that spec person, not only it's, not only used to say the deprecated, it's also to provide some more metadata, so you can have some mechanism that is checking okay, there's something deprecated that send an email to subscribers. Whatever exactly so, you could probably alert.

A

People there hey it's one month until this is gonna, become the brigade you better and that she would update your code right. Otherwise this will stop working or yeah yeah right, oh and.

D

Did you check the graph kill because for graphical I would say the use case is pretty similar because you don't deprecated the whole API, but a specific query or mutation and as far as I know it's only now. You have directive I, think deprecated. Well,.

A

Yeah this exists on schema the, for instance. This will be markets deprecated. This is already possible and JSON schema by using deprecated, true, okay, but would but that's about the message right. That's about the content of the message, but important for operational reasons. You don't want to have these two topics right because it cuts you money, the more topics you have and and and it becomes like, like zombies there right, like topics that are there, but nobody's within or or or some people are using. This and some people are using this this one.

A

Then new services might be subscribing to the old one. So you and that's having to maintain to write.

B

A

For operation reasons you want to delete this topic from calf:cow delete this topic from profiting cue from solace from wherever you want right. You want to free users, that's it it's not just the message right! That's the what you say what you say about graph QL, it's really possible at the message level you can mark a property is duplicated, that's what they put it, but yeah! That's what we're talking is a channel level, usually the topic.

A

C

Makes sense I mean here, it's always we're trying to define a kind of a topic structure, a standard topic structure. We can use internally and it will have a version number in the topic. So you.

A

C

This is totally aligned with that very simple to a lot of rest api's that have a version number in the anywhere I yeah. That's that's what.

A

I, usually people telling people that usually have long you're around pattern- let's say right or recipe for naming topics, so you include include the version and on the topic trade could be here could be at the beginning here, somewhere I actually have a proposal for that, but I had to move it out from Maison kpi to my own repo to my github account, because people were thinking that that was mandatory when using it. Since API.

A

Sorry in the beginning, you think API were just my my notebook, my notebook right for for even doing the detectors and I left it there, widows thinking that it was going to become this right, so so yeah so I think yeah I will have a look at this external dr. link or whoever, and probably the also have a look at them. Deprecated deprecated, true plus the sunset, maybe and as you Michael said- that it might be worth did have this everything he will be optional.

A

C

A

C

Fully if they are to go to my next meeting so yeah.

A

C

A

You just sorry for that which would probably have started with you. Can you please summarize quickly? What's the status of the of the code generator for spring cross stream? Yes,.

C

Let's see I made a couple of small changes like, for example, I'm, using some specification extensions to specify things that spring clouds dream needs like something called a consumer group, and you know queue name and stuff, so originally I had those on the channel, but they're only relevant to really a subscription, so I've moved those down into subscription. So there's a couple of small changes like that, then I'm gonna finish up today and I want to do a bit more testing.

C

You know with a few sample documents, I've got and if everything works and I going to do over request tomorrow,.

A

Don't feel bad or anything for pushing draft code, just if you want to whenever you want just create, even if it's incomplete, just create a draft pull request and because people just can can just jump in and help you write so I'm told you like, hey, Michael I will take care of this part. While you work on this other thing and then you can clap right there or people can start early, removing the code and making suggestions, or you know so.

A

Okay, good yeah, okay I mean that it's, it's usually a good, a good way to come right by it, not waiting to it until the end. So only early sharing is actually. It will be better for you as well yeah.

C

Okay, okay! Well it's more than so. Okay, thanks guys, I'll talk to you soon. Thank you. Hey all right, respect.

A

Okay, Lucas so I think it's you and I. Now where's Jonah's euros were missing you and how.

D

Much time you you want to live for comments on the channel.

A

For comments under what sir, oh, they.

D

On this channel topic, I'm.

A

This thing yeah, actually not I'm, not considering it like super urgent, I'm, just starting to survey people and they at some point. At some point, we will have to put the schedule for the for the feature right right now, just surveying people to see what they think about it.

A

Well, what else we have these things on the generator package, which I think we will have to.

A

So thing about this is don't know Lucas if you know, but so.

A

The generator has the generator templates right.

A

They all have. Let's take this one, which is the mosque ultimate I, think so they have some things like. It's called filters right and filters it's in its nan Jiang nan, Jack's name for helpers.

A

It's just helpers for the template, so, for instance, if I want to nan Jax doesn't have a way to convert a string to tip up case or to KML case or anything. So you can create. Add filter, give up case, Kindle case right, and then you can use it that then you can use it on the on the templates.

E

A

So I don't know I think, for instance, the package.json I think has something maybe now I think it's a comfy.

A

Okay, so, for instance, this one is: is it it's a chain of helpers, so it's taken a sink API channel names with families, so these are all the channel names containing the fabless operation, translating them to include topics dump.

C

A

Something that exists on venjix and safe as well, so this is like this is like.

A

The json stringify this is x, json, stringify, dump and safe is just to remove unsafe characters from being.

A

Output right, so, if you come here.

A

You have this to mqtt topic, which is one of the things that we were using there. It takes a list of topics and then our blasts, the things that you can have logic to the template in small functions, with a name right and then you can use them on the on the on the template to do to do certain things. Stuff.

A

The thing with this is that if you go now, if I go down here,.

A

I wasn't an odious one, so I go to the HTML filters.

A

This might not be a good example, but.

A

Let's try this one.

A

Yeah, so if I come here, for instance, you will see again give up case can make a new case again. The same faction functions defined over and over and if, at some point, I want to change this I will have to and I want this to be propagated to all the templates. I will have to go to every template and map data templates. You know it's and also we might not be able to update every template, because people can create their own templates right so and they will not be pushed here in the generator River.

A

So so yeah there's no there's no point on.

A

There's no point in trying to control it in there right, but the thing is there: there are a lot of duplicated curl like like this ones like, like all I, will say most of the string methods for for low des or underscore they own.

A

Almost all of them are present in in some way in all the templates, like kebab KSK no case, this will be very common in every because I mean because you will have to transform strings and names to one of those, depending on the link on the premium language you're using right, so it may have some.

A

It may be good to extract it to to become more accustomed to like a library of predefined filters. So you don't have to let yourself to your templates and you don't have to maintain it right.

A

That's one way this is abstracting them so put putting them on the on the generator generator level as an SDK right.

A

So that's one way: that's one thing, then this has become a problem recently thing it was Michael who raised the issue first. The thing is that, for instance, I want to use certeyn a simple example to generate code. We would like to use things like quick type library that exists to generate to generate types from the JSON schema definition. You can generate Java poachers or Gogol instructs or everything right in every language. So you don't want to do this yourself in your template right.

C

A

Want to have a library that will give you the result and like this you will have many other stuff. So in your template, you want to install a dependency for your template or your template to use during generation, not as the resulting code. You know what I mean so yeah you're in generation of during the generation. I need to use this dependency. Probably this dependency will be will be done on the on the filters. So the filters you want to do something.

C

A

You will have to put require something, and these filters are so the package essence for this, for the for the filters is actually the the generator package, so you cannot put the dependencies on the generator package because then it this will be a dependency for for everyone for him template. So then, if we do this, the number of dependencies will keep growing and growing and growing to serve all the purposes right.

A

So it will be great to have a way to define dependencies for the templates, and so what came to our mind is maybe the templates itself, so the packages themselves separate the packages right. So one of the one of the things we could do here is each of these templates. Here we could remove them from the or we could leave it here, but we could remove it from here and then create a separate package for for each of the templates right. Each package will have their own annotation and all the stuff right.

A

So then you can control your dependencies and then the generator will be in charge of installing the dependencies of the template before right before generating the the code or the documentation before generating exactly you know, you know what I mean in follow: yeah.

D

So there, basically, you would like to have a like a mono repo generator would be a a repository of different, let's say, different projects. Each of those templates, as I said different package Jason.

A

D

Them sorry could.

A

Be mono repo or not. The thing is that we could have the thing again.

A

Someone probably has a yeah I know that some people have templates private templates for them in their companies that are not here and they are not willing. So this will be also.

A

It should be possible for them to specify dependencies or on their templates right. So again we will not control all the language never and then- and that's not the vision. So the vision is that people can print around templates. They can pal this or maybe not, but this will all work the same way right so so yeah. So it's not so much about them on a repo. Not is probably we. We can leave this ones here as a mono repo, and then we could have packages all the packages inside. That's fine I'm, fine with that.

A

But again we will be able to control all the possible.

D

Yeah, but if you would make sure that they can work as a separate projects, then of course anyone can do it with their secret templates.

E

A

That's the point, so probably we can I think we can. We school should have issues for those right yeah which would create issues from this one. That was the outcome of the previous of the previous meeting, and so yeah I think it's. It would be right and implement the weight during classes or ties from this and schema definition yeah.

A

So because of because of one of the most common use, cases is gonna be generating code, so the most common use case is because I don't know any other use case, for the generator is jared code or generate documentation, I, don't know any other use case, and because there are many programming languages most probably we will. We will have some more code, generators than documentation, generators right.

A

So one of the things that the generator could offer to the templates is again as part of these generator SDK or something it could be a filter made that will offer hey. You call this method here and we'll give you the if you're, if you're working on a Java template, you call this method and it will give you the Java poacher for this schema definition or if you're working on a Python or a goal.

A

Template will give you the ghost tracks. You know what I mean, so people don't have to work this themselves, because otherwise, what's gonna happen, is that very quickly? We'll have many many templates, because it's already happening that, for instance, one will have a problem when generated the Kajal is here, but it has this feature. There is really mandatory for my use case, but then there's in this other template that doesn't have the feature I need, but it's better at generating the pojos. You know to avoid this is inconsistencies with common stuff.

A

We could probably offer this as part of the update generator right, and there is a library for this, which is it's their quick type.

A

That's to me, man. This.

A

That's it's my my day. So, for instance, in the left side you have a JSON schema definition for latitude for coordinates when latitude, longitude and test with one on/off and all the stuff on the right side. It gets killed in Java. So it tells you this will be a coordinate, dot. Java file. Here you have everything that so that should be there and then you have a test Java, which I guess is this test?

A

And yes, so yeah? And actually it's yeah. It's on the same package? Okay, so you can. You can use it from here test. You know a curious account, that's the cool thing and yeah totally valid code and if I use go, for instance, it will create those tracks from this JSON schema and since we're using JSON schema for the messages and for the scheme as an a-lister. So we could leverage this this library and look at this.

A

It's this it's you can choose a lot of languages right like typescript and it will generate attachment for for you. It will generate the types right order interfaces in this game.

A

There are many languages really, so we could probably offer at the generator level as a way for templates to say: hey I want the Java class here right in this file. I want the ghost tracked in this other template and they will not have to maintain it. So people will not have to maintain this logic like personal JSON schema and generating site yeah.

A

We will maintain it or in this case quicktype will maintain but yeah so, let's say Jas library right there is library, so we will be able to use it. So we've been lucky.

A

What else yeah?

A

Okay? So that's! uh That's it from there.

A

We we've been today with discussing an issue that well before we before we continue can. Can you please create an issue for each of these bullet points? Maybe if not today, tomorrow, no.

D

No exactly exactly that's what I wanted to propose. I was just left question to make sure that the third but no bullet but pulling the button and bullets fine I handled properly, so that this quick type functionality of generating types and classes for whatever language or structs. That would be something like optional right. It would be just part of the generator api that you can create them exactly. It's not some additional feature. It.

A

Something you could use right something, but you don't have to like, for instance, in the case of documentation, generators you might not want to use it right or maybe yes, maybe you want to give people a copy pasted right there, so people can copy themselves, but that's yeah, that's option.

A

You know that more than anything like having away alongside with your documentation, to have on the right side, for instance, along with the wit examples you have to, for instance, Java or JavaScript or typescript, or go wherever, and you can copy the classic medium or distract attention from there yeah that's. This could be useful, probably more than the code generator, because people some people are very skeptic of code generators. So well, so that's.

A

Right want to say something about it.

D

So they have to Michigan itself, like I. Think it's pretty straightforward. The most important is the site's discussion that we had from about this automation, so the the whole flow of working of the repositories where we tackled the topic of working on Forex, having only master that is protected from the indirect changes without PRS.

D

So looking on the discussion under these two looks like at least you me and Yanis. We we like it. We agree to it, and but I also mentioned at the bottom, and that we could also go even further with such a number that maybe we should have a pretty strict approach, also to merging policy to have also clean history. Our I didn't see the last comment.

D

D

And the where was I, oh yeah I saw the the policy for formatting. So do not let anyone create pr's, for example, with five comets and we merge it. Then we have the pretty dirty history of the the project. So I would even go further with suggestions like okay, let's have squash in March, squash and marriage as default for merging, etc, etc. And my suggestion maybe would be because it's a something excites to the topic of automation. Maybe I would create a like a list of things.

D

I think we we should like standardize, get an opinion of others and then just apply globally to all the repos. If we agree or not so I think I mean that's what I'm gonna I'm gonna do, especially that if we really reward everyone switches to work on, Forex would be nice also to have like simple instruction for everyone to set properly the settings on the fork on your local to know what have pains with always updating master on your fork, etc. To have it automated yeah.

E

D

Let's yeah, so let's not do it overnight, so I'll just scratch a an issue with the description. What we could change our.

D

A

Forks is like, but.

D

Only sounds really I mean I. Remember when we tried when I started, introducing it into in in keema and, like 90% of developers, were used to like working directly in the repo, and there was like a lot of pain, but at the end over they, everyone switched it's. It's really not a pain at all, and at least you have clear branch, history, no orphans there, yeah.

A

That's the story will be cleaner. There will not be some be branches there.

A

Yeah cool so I, like it I, mean I'm totally into this, even though I don't like it like the water works, but I mean I I'm happy with this, because it's not that it's not such a problem for me to change this to this way of working right. That's that's why I said like yeah? Actually it's here I'm having to take the path I get me said meatiness, but.

C

A

Fine with any process as long as we all agree right so as long as we're all doing something, that's fine. What I don't like is is it some people are doing something blending other things. I know this is an exception. Then confusion starts right so today, as long as we all agree with something and buying doesn't mean that which will be our first choice or, for instance, working with with Forex will not will not be my first choice but I'm happy.

A

D

Then, if we choose it at the end for sure I'm gonna create a easy to use script, that it's gonna, be easier for. Anyone to start contributing yeah.

A

Sure cool so yeah, let's forget that's my examples.

A

So, coming back to the generator I'm gonna I'm, just gonna mention this. So it's it's recorded and people can look at it. So this guy's Stefan Seeger created this e. So today, which is about supporting bass, the bass tag HTML base tag on the HTML template. So when you click on it on the under sorry.

A

So here on the HTML documentation this one when you have linked what that's not a good example, have been.

E

A

So this one, for instance, let me try to find something.

A

Anyway, if you put a link here somewhere, a relative link, it will be pointing to the root of the of the domain right because that's the root right. So what he's suggesting is that laying some forms here the base URL for the links and forms could be changed right as a or instance, with a parameter, so imagine that they deployed this. This documentation, not at the root level, but they have this async talks. That's when it was proposal, man that you I hit enter now here and I see this documentation.

A

If the links are pointing to the root, they will be broken right and that's what happened again right now. He wants to present the acing des dogs right, which is something that we will also benefit from on the playground by the way.

A

So, whenever you embed the playground on a imagine that you have my company facing a playground and it entered there, you see this this playground, it's a symptom. We will. We will want to.

A

To have the links relative to a cincher period as playground right, that's relative to the slash to the root mm-hmm.

D

A

So well, so that's a little bit of context that the guy was realized at and very responsive. It was all today and he created a pull request, which I already proved by the way. So you can have a look later. If you want it's as easy as this, if you pass a param mase href, it will have this HTML on the head on the head of the document and then on the index.html file. So nothing really fancy insist. Is it works?

A

The thing here is here now is how do we know and that's my issue now? How do we know how many or which parents a template supports right because the HTML the HTML template supports it, will support base base href and an another one which is sidebar organizations?

A

The sidebar could be organized following different different things, different ways of sorting the information, and so it allows you to specify those two parts and, and then, for instance, the node.js template supports the server pattern, which is when you're generating the code, and you have three servers and they on your recent keep a file you might want to generate the code for a single server right right now. This is the only way to go.

A

You generate the code for a specific server, so the configuration file will take the information from that server, not from not giving used.

A

Thing is it understand what what parents are a template supports? You have to either look at the code and check for this, if perhaps without whatever, and then you understand what it is or the other one is by ourselves manually put in put it on the on the documentation and on the readme file for the template, but that's very easy to forget and very easy to really maintain my proposal is. We only have TP config JSON file, which is template, comfy, right and.

A

I'm going to show you an example of the template, comfy.

A

So no GS is a good example. It has a TP config file, which is a special kind of file that it will not be copied to the result to the resulting curve. So this is file it's ignored in the output, and you can put information about your template here like, for instance, I only support this template only supports in QP and ktt Kefka WebSockets. If you specify other protocols, it will tell you that, so the protocol is not supported. It requires you to specify the center bottom.

A

So when generating the code, you have to pass the parameter server, the parameter server, it's mandatory and all the files here inside the middle middle Wars folder, and this one here are non-renderable files. What does it mean? It means that they are not in place there nothing place. This will be copied as it is. It's copy.

A

The code, the key thing here- is a required forums, so we already had something about parents, but we don't have a way to say these are the parents that the template support? We only had a way to say that these forms are required.

A

So my proposal is to have something like this parameters. Basic trip, description right, but then, because I realize that we already have the required forums. I thought. Ok, so probably we can read off. We can get rid of the required parents configuration and on the typical vacation file, and we just have the parameters server description. We say if it's required not by default, if you don't say anything stuff required. Thank you. If you put to be quite true, it would require right and then.

A

You make the generator check whenever you do this code. You have this code, we could check if my undefined parent has been defined here from the list of parameters and if it hasn't been defined, it will trigger an ever right.

A

So it will force you to define the supported parameters on the on the typical config file, and so that's one way to enforce documenting in a machine readable way.

A

The firm's the cool thing about it is that in the future we could create a generator or a map using the terminal generator now, but we could have a another library to to to generate and readme for for the for your template, you pass your template, key, become fake file and it will generate a with me for you or even on the on the command line.

A

Let me check here so, for instance, on the command line. We could do things like.

A

Surfaces, AG sping, along user generated myself, I've been telling people how to use it in so so we have AG and I. Have my async API file I want to use the nosiest template and if I do this like this right now, if I have days in Japan on file, which is not the case, it will be valid.

A

Will fail anyway, because we said that the server param is required. You need to pass the server part right, so we should have something like this server, the close protection, and so that's what it, what it, what it is. The cool thing about the heaven de cinéma in the machine readable way is that at some point we could add things like I.

A

Don't know, I want to I want to have a g-dub I mean printing, that's in the syntax here now, GS, ok and it will show you a list. The list of parameters you like I hate, so no GS template will require you to specify the server parameter, and it also has these other parameters that you can use to tweak the result, but they are not mandatory, but it's there and it's documented. So people can discover what can they do it with with the templates?

A

So, yes, I think so that's that's. It basically I think we can in some way we can enforce people to document the the parameters and probably in Android in the future. We can even require here that you describe using JSON schema, for instance, the type of the parameter, if it's a string, if it should be an array.

C

A

It's all the stuff.

A

Well, that's too much for you, so it doesn't make sense yeah it makes the constants yeah cool, so I think we're gonna start closing now before I. Stop. Recording I would like to thank you a lot for for joining, so this is now recorded thanks a lot for joining me in KPI and yeah big round of applause, for you looking great can take business together. This is the first one of many successful meetings from chef's meeting. Even worse, we're.

E

Gonna rock for sure, oh of course, cool.

A

So I'm gonna stop recording, so we can start with the beers.

A

Okay, I, don't think I stopped.