Skip to content

Conversation

david-a-wheeler
Copy link
Contributor

Currently configuration is mostly in a YAML file embedded in the lab's HTML. This means that the lab configuration cannot be shared between locales (translations), which is annoying.

We can't easily load YAML or JSON from a separate file when running or testing locally. However, we can easily load a separate file if it's in JavaScript format.

This switches the configuration of lab hello.html so it uses the configuration in hello.js.

Currently configuration is mostly in a YAML file embedded in the
lab's HTML. This means that the lab configuration cannot be shared
between locales (translations), which is annoying.

We can't easily load YAML or JSON from a separate file when
running or testing locally. However, we *can* easily load a
separate file if it's in JavaScript format.

This switches the configuration of lab hello.html so it uses the
configuration in hello.js.

Signed-off-by: David A. Wheeler <[email protected]>
Signed-off-by: David A. Wheeler <[email protected]>
This does not *implement* translations, but at least this
includes some translations (which we hope to use in a later
change).

Signed-off-by: David A. Wheeler <[email protected]>
To make it easier to move from YAML, automatically detect
differences between info and info2. We can create a JavaScript
file that looks clean but is *supposed* to be identical, and
once done, eliminate the old version. This will help ensure
we don't make mistakes during the transition.

Signed-off-by: David A. Wheeler <[email protected]>
@david-a-wheeler david-a-wheeler merged commit f5f0b60 into main Jan 29, 2025
5 checks passed
@david-a-wheeler david-a-wheeler deleted the lab_hello_yaml_to_js branch January 29, 2025 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant