Open DamianEdwards opened 4 days ago
I think NodeAppResource
might be the outlier here. Mostly, we put the Resource classes in Aspire.Hosting.ApplicationModel
. For Azure, they all are in Aspire.Hosting.Azure
. Python, and Dapr each have Aspire.Hosting.XX
.
A sample of other resource classes:
Milvus also appears to be an outlier.
All Azure resources are in Aspire.Hosting.Azure
except the following:
Hmm OK. Seems we haven't been particularly consistent with this ☹
Is there an existing issue for this?
Describe the bug
PythonAppResource
is in the namespaceAspire.Hosting.Python
, whereasNodeAppResource
is directly inAspire.Hosting
. This is inconsistent, we should putPythonAppResource
inAspire.Hosting
.Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version info
No response
Anything else?
No response