You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2025. It is now read-only.
As you can see, having a name only is not enough to query BaseService since at that moment BaseService is not loaded/resolved (builder.model.node['types'])
I do actually have a local fix for that, that adds uri to ClassReference (I'm not sure but I feel like it makes the most sense to put that information there):
and I'd love to submit a PR, but I'm not sure if that's how the model should look like? another approach would be to make name a qualified name, like so:
I think we're not ready to get into this level of detail here yet, there are bigger questions about the macro metadata model that we need to figure out first.
TL;DR do we want a
ClassReference.uri
field? or maybeClassReference.name
to be aQualifiedName
?I'm currently building a macro that will take in a specification as an argument and generate a client/server based on this specification
the way it's going to be used will be something along the lines of:
which generates the following:
As you can see, having a name only is not enough to query
BaseService
since at that momentBaseService
is not loaded/resolved (builder.model.node['types']
)I do actually have a local fix for that, that adds
uri
toClassReference
(I'm not sure but I feel like it makes the most sense to put that information there):and I'd love to submit a PR, but I'm not sure if that's how the model should look like? another approach would be to make
name
a qualified name, like so:So my question is, do we want a
uri
field,name
to become a QualifiedName or maybe something else?Thanks in advance!
The text was updated successfully, but these errors were encountered: