ForNeVeR / ForNeVeR/Cesium

SDK should not trigger generation of `.runtimeconfig` by compiler

Open
#960 2 comments 1 reaction 0 assignees View on GitHub
area:sdk good-first-issue kind:feature status:help-wanted
Dominant language
C#
Stars
451
Forks
49
Avg merge
13h 59m
Merged PRs (30d)
6

Description

Cesium Compiler has an inherent ability to generate `.runtimeconfig.json`. This ability is implemented mostly for the console compiler use.

Cesium SDK, on the other hand, relies on the `.runtimeconfig.json` generation introduced by the common .NET SDK (see #946 for details).

In the logs produced when compiling a project via Cesium SDK, there are also traces of the `.runtimeconfig.json` being generated by the compiler — which is then subsequently ignored.

To reduce the confusion, we should introduce an option for the compiler to skip generation of the `.runtimeconfig.json` — and this option should be utilized by the SDK, so that no redundant work is done or logged as being done.

The behavior of the current command-line compiler (generate the `.runtimeconfig.json` by default) should be left as-is.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.