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
Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.
2. A failing test has been provided
3. A local solution has been provided
4. A pull request is pending review
Describe the bug
When generating a OData endpoint, I ran into an issue that one of the entities was called import.
This conflicts with an existing typescript keyword, and so the code caused errors.
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
When generating a OData endpoint, I ran into an issue that one of the entities was called
import
.This conflicts with an existing typescript keyword, and so the code caused errors.
an example snippet from the
types.ts
file:To Reproduce
Steps to reproduce the behavior:
(Can't give you access to this OData source)
Expected behavior
Code works as expected.
In order to avoid namespace collision, perhaps the
mesh build
step can create types with the namet__<name>
instead?Environment:
The text was updated successfully, but these errors were encountered: