Comments (5)
Thanks @brenovieira
I am wary of renaming. I think it will lead to confusion, especially when it comes to the Models.
The full namespace would work but gets a bit ugly to look at. We'll get something worked out. Expect a new release in a few weeks along with the sources to get populated into the repo too. Leaving this open 'til we get the fix in place.
from autorest.
This scenario should work as of 0.11.0 since now we are generating usings inside the namespace
from autorest.
@stankovski , 👍
I believe that is right !
from autorest.
@stankovski , please reopen this issue.
I updated to 0.12.0 and it generated the same problem, even with usings inside the namespace.
Please, see what it generated (part of) in this gist.
The lines - 59, 135, 142 - don't compile since it has Action, which is defined in namespace Models and System.
On line 7 you add using System
and
on line 20, you add my namespace using Models
.
So you define both and it has an ambigous reference.
note:
I have the same issue with a class called Group. Error:
'Group' is an ambigous reference between 'API.Cliente.Models.Group' and 'System.Text.RegularExpressions.Group'.
note2:
I'm not sure I had this issue with 0.11.0 as well or not.
from autorest.
Tracking via: https://www.pivotaltracker.com/story/show/107076350
from autorest.
Related Issues (20)
- [openapi to tsp] Fix `accept` header logic
- [openapi-to-typespec] Replace `@projectedName` with `@encodedName` HOT 1
- [openapi-to-typespec] Use `union` instead of `enum`
- [openapi-to-typespec] Create a tool to sort JSON properties to compare swagger diffs
- Non list API requiring a GetAll method in SDK generation
- Pass compilation for all the test projects
- Compilation fail with error " didn't specify which versions with @useDependency."
- @versioned is used without module import
- ApiVersion as path parameter not supported in openapi-to-typespec
- @encodedName don't support "json" as mime type
- Express resource hierarchy
- error | Modelerfour/IncompatibleRequestBodies | Operation 'Imports/PostImportInGroup' content types [json, multipart] have the same body schema but cannot be used together
- AnyObject as body is not correctly generated to typespec
- parent resource should be a model in the generated tsp
- autorest warning on .Net 8 app during the build process
- Improve error message if "parameters" contains "$ref"
- Add converter version info to the result
- Collison detected inserting into Object: transfer
- Improve error message "no input files provided"
- One page of issues in openapi-to-typespec
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autorest.