[Ideas] Ideas for vuerd in future

[peterstriz]

I would like to ask you what you think of some ideas I would like to implement. Some are very easy and same may take longer and may change some functionality of vuerd.

• (Idea) Have option to have diagram read-only so we could somehow show anybody how our GraphQL endpoints look like on live database

• Make working with VSCode extension much easier - add some better communication that can be easily expanded

• [1 of 2] [Request] Colors #212

• [Request] Make autocomplete easier #213

• [Request] Default values to table #214

[dineug]

1. There is a readonly option. <erd-editor readonly></erd-editor>

2. Let's also consider upgrading the VSCode extension environment.

• For communication, it would be better to use GitHub discussions.
• I don't think real-time chatting will work well because I have to rely on a translator.

[dineug]

The vscode development environment has been improved.

$packages/vuerd yarn serve:vscode
# And
# Run Extension (vuerd-vscode)

[andrzejzysko]

What about generating table as HTML to put it in documentation like: Word, Confluence, etc? Maybe as Generate Template?

[oSethoum]

Hi, I would like if you add two more functions to the code generator, plural and singular so we can make code generation easier.
plural will pluralize English nouns.
singular does the opposite.

[the729]

Import from DBML?

[oSethoum]

Add a way to add custom options for code generation, example am generation a GraphQL API from vuerd json file, I would like to add sub: true to the columns I want to register them for subscriptions.

[filiscas]

It might be possible to hide the columns so they don't show up in the visualization

[Androphin]

I second @the729 request and maybe also import from SQL DDL.
Another thought that came up my mind is live editing a remote database visually.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.