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

When outputting SVG, the image is the path of the file.

Portability is not good because the file path cannot be referenced at the time of distribution.

Describe the solution you'd like

Base64 encode the image and embed it in SVG.

Display the execution status etc. in an easy-to-understand manner like jest.

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

The GCP icon has been updated, but it is not supported.

Describe the solution you'd like

Update the component icon to a new one.

It also supports new services.

Additional context

https://cloud.google.com/icons

Problems

There are a lot of packages, and it is difficult to understand the dependencies and purposes.

How to solve

Create a diagram that visualizes dependencies to increase project transparency.

Describe the bug
If upstream and downstream are mixed, the orientation described earlier has priority.

• Example code

<AppEngine
    name="ExampleA"
    upstream={["ExampleB"]}
    downstream={["ExampleB"]}
/>

• Expected diagram

ExampleA -> ExampleB
ExampleA <- ExampleB

• Actual diagram

ExampleA -> ExampleB
ExampleA -> ExampleB

Describe the bug
When I wrote AWS twice, it was displayed combined.

• Example

    <AWS>
      <ContainerService
        name="exampleA"
      />
    </AWS>
    <AWS>
      <ContainerService
        name="exampleB"
      />
    </AWS>

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

The exceptions of the rediagram component cannot be handled and the error is difficult to understand.

Describe the solution you'd like

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

Additional context

Display known errors such as useAssertProvider in an easy-to-understand manner.

Ideas

• Add an example diagram of a multi-cloud configuration to the gallery.

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

Visibility is poor because the color and type of the tip are the same.

Describe the solution you'd like

• Allows changing the color and style of the edges.
• Allows specifying by edge color or style theme.
• Edge is automatically color-coded.

Describe the bug
An error occurs if you specify a directory that does not exist.

** How to solve**

Create a directory with ensureDir etc. in advance so that an error does not occur.

Is your feature request related to a problem? Please describe.
If there is no dot, an error will occur when executing rediagram.

Describe the solution you'd like

Prompt to install graphviz during create-rediagram-project.

Allow settings related to rediagram operation in the rediagramrc file.

I caught the below error.

$ git clone https://github.com/kamiazya/rediagram.git
$ cd rediagram/docker

// I wrote a model that same as the example in README.md.
$ vim MyInfra.rediagram.tsx
$ make build
...
$ docker run --rm -v `pwd`:/workdir/ rediagram:0.1.1
(node:1) UnhandledPromiseRejectionWarning: Error: Command failed: dot -Tpng -o MyInfra.rediagram.png
Warning: No such file or directory while opening /node_modules/@rediagram/aws/assets/general/Client.png
Error: No or improper image file="/node_modules/@rediagram/aws/assets/general/Client.png"
in label of node Browser
Warning: Arrow type "point" unknown - ignoring

    at checkExecSyncError (child_process.js:630:11)
    at Object.execSync (child_process.js:666:15)
    at Object.renderDot (/node_modules/@ts-graphviz/node/lib/index.js:51:15)
    at renderToFile (/node_modules/rediagram/lib/render.js:13:12)
    at render (/node_modules/rediagram/lib/render.js:17:5)
    at Object.PNG (/node_modules/rediagram/lib/render.js:27:5)
    at Object.<anonymous> (/workdir/MyInfra.rediagram.tsx:5:1)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Module.m._compile (/usr/local/share/.config/yarn/global/node_modules/ts-node/src/index.ts:1043:23)
    at Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Is your feature request related to a problem? Please describe.
I use the title bar of GCP a lot, so please support it.

Describe the solution you'd like
Please refer the title bar in official sample.

When executing multiple files from redigramc CLI, use worker_threads etc. to enable parallel execution.

Describe the bug
When using TransferFamily, icons are not shown.

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

Two-way communication cannot be expressed.

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

Although there are groupings such as VPC, it exists only in AWS and GCP packages, and it was not suitable for abstract discussions that do not depend on specific infrastructure.

Describe the solution you'd like

A component that expresses abstract grouping such as Group is provided from the rediagram package.

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

There is no way to represent a GCP folder.

Describe the solution you'd like

Add a folder component.

Consider the hierarchy of folders.

Additional context

https://zenn.dev/kamiazya/scraps/6b86bde6576c2b

Describe the bug
I tried yarn start and following error is occurred.

src/MyInfra.rediagram.tsx
(node:24669) UnhandledPromiseRejectionWarning: Error: spawn dot ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

To Reproduce
Steps to reproduce the behavior:

> yarn create rediagram-project my-rediagram
> yarn start

Expected behavior
Success yarn start, without errors.

Screenshots
If applicable, add screenshots to help explain your problem.

• OS: [macos catalina 10.15.7]
• Node.js version [14.x]
• Package Name
  • create-rediagram-project
• Package Version
  • latest

Additional context

I tried to catch error. Result is following;

Error: spawn dot ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn dot',
  path: 'dot',
  spawnargs: [
    '-Tpng',
    '-o',
    '/my/project/dir/my-rediagram/img/MyInfra.rediagram.png',
    '/var/folders/fr/5qmpnmcs41v1ypvgv454y6c40000gq/T/tmp-27783-vtNDIm2O94H7'
  ],
  cmd: 'dot -Tpng -o /my/project/dir/my-rediagram/img/MyInfra.rediagram.png /var/folders/fr/5qmpnmcs41v1ypvgv454y6c40000gq/T/tmp-27783-vtNDIm2O94H7',
  stdout: <Buffer >,
  stderr: <Buffer >
}

This is occurred at here https://github.com/ts-graphviz/node/blob/master/src/executeDot.ts#L25 , i think.

I don't remove ./my-rediagram/img folder.

tmp-promise has something wrong?

thanks.

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

The create-rediagram-project command does not support yarn.

Describe the solution you'd like

Allow the user to choose between npm and yarn when executing the command.

Problems

Since rediagramc only executed the target file once, I had to execute the command every time and the experience was not good.

How to solve

Provides an option to detect file changes and allow re-rendering with the redigramc CLI.

The cause is as follows: the path pointing to the icon is incorrect.

Currently, it is output in console.log etc., but it seems better to provide a correct logging method as a framework.

Describe the bug

When the type of Glue component of @rediagram/aws package is set to Crawler, the path cannot be resolved and the image is missing.

<Glue name="sample-crawler" type="Crawler" />

Check lint rule and build, test if possible.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

• OS: [e.g. macos, windows, linux]
• Node.js version [e.g. 10.x, 12.x, 14.x]
• Package Name
• Package Version

Additional context
Add any other context about the problem here.

Create a starter kit to make it easier to create a rediagram package with the command below.

$ npx create-rediagram-diagram
$ yarn create rediagram-diagram

If you just want to update the markdown documentation, don't run tests like Node.js.

Is your feature request related to a problem? Please describe.
If the paths cannot be color-coded, overlapping paths will conflict.

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

The project created by create-rediagram-project has no coding rules, so maintainability may deteriorate.

Describe the solution you'd like

When creating a project, install code formatting tools such as eslint and prettier in advance.

Describe alternatives you've considered

Add options to the cli and let the user choose if they need a lint mechanism.

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

The error is not handled by cli.

like this issue.

#97

Describe the solution you'd like

Display the error details appropriately.

Introduce unit tests.

Use jest-graphviz.

Is your feature request related to a problem? Please describe.
AWSに詳しくない顧客やメンバーと会話する際に、AWSのアイコンがどのサービスを指しているのかわかりずらい

Describe the solution you'd like
AWSのアイコンにサービス名を出せるようにすること