When a schema has no type - x-env-value does not work

Open
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start by tracing how schema types are handled during x-env-value evaluation, using the log level enum case described in the issue. Confirm the behavior when the schema type is undefined, then verify that an environment value is evaluated for that case and cover the result with a regression check.

Written by the indexing model from the issue text.

Description

bug

For example the log level setting is an enum, so its type is undefined.
the current behavior is that the the env is not evaluated which is undesired.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MapColonies/config

All issues in MapColonies/config

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.