Closes #12

The code successfully executed on windows with expected results, without modifying the code. However, transforming the directory paths to a unified format may save us in some cases.

Welcome to WhiteSource Bolt for GitHub! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.

:vertical_traffic_light: WhiteSource Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable WhiteSource Bolt for GitHub, simply close this Pull Request.

What to Expect

This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource Bolt for GitHub will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.

If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.

:question: Got questions? Check out WhiteSource Bolt for GitHub docs. If you need any further assistance then you can also request help here.

Is your feature request related to a problem? Please describe.

The users may want to put the generated files to a desired directory.

Describe the solution you'd like

A flag, preferably `-o=path/to/output/dir", can help.

Describe alternatives you've considered N/A

Additional context N/A

type Example struct {
  ID string `uri:"id"`
}

for example this will generate:

export interface Example {
	"`uri:"id"`": string;
}

and should generate:

export interface Example {
	ID: string;
}

A the name should be used as a fallback for a json label.

Here is a happy flow with json label:

type Example struct {
  ID string `json:"id"`
}

export interface Example {
	id: string;
}

Beep boop. Your images are optimized!

Your image file size has been reduced by 81% 🎉

Black Lives Matter | 💰 donate | 🎓 learn | ✍🏾 sign

📝 docs | :octocat: repo | 🙋🏾 issues | 🏅 swag | 🏪 marketplace

In Go you can use the special iota expression for auto incrementing values of an enum. This should be supported in GoDMT by translating those enums to the correct value (based on position)

Describe the bug When a struct has a field that is an imported entity, and in the form of a slice of those entities, the translation is not correct.

Expected behavior

Media       []ProductCategoryImage `json:"media"`

would produce:

media: ProductCategoryImage[];

Actual result

Media       []ProductCategoryImage `json:"media"`

produces:

media: ProductCategoryImage | null[];

OS (please complete the following information):

• macOS
• Big Sur

There is actually no valid reason (apart from laziness) to use the reflect package for GoDMT. Reducing its usage as much as possible will bring more performance, type safety, cleaner code and more handling of edge cases.

Some creativity and investigation will be required for this. My idea is to create a second class perhaps and an instance property of the parent class whose type is the 2nd class.