Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

use ruaml instead of pyaml #51

Open
vnadot opened this issue Mar 2, 2022 · 2 comments
Open

use ruaml instead of pyaml #51

vnadot opened this issue Mar 2, 2022 · 2 comments
Assignees
@gohierf
Labels
enhancement New feature or request

Comments

@vnadot
Copy link
Contributor

vnadot commented Mar 2, 2022 •
edited by gohierf
Loading

Reasons:
@vnadot vnadot added the enhancement New feature or request label Mar 2, 2022
@gohierf
Copy link
Contributor

gohierf commented Mar 3, 2022

As far as I understand you would like that WeTest accepts duplicate keys ? What use case do you have in mind ?

@gohierf gohierf added the wontfix This will not be worked on label Mar 3, 2022
@gohierf
Copy link
Contributor

gohierf commented Mar 7, 2022

Ok I didn't get it at first because of the partial description of the issue.

You suggest using RUAML instead of PyYaml because PyYaml doesn't output any warning when a duplicate key is used.

Currently PyYaml just ignores duplicated keys and uses the latest value read.

Seems OK for me to switch to RUAML for WeTest.

@gohierf gohierf removed the wontfix This will not be worked on label Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gohierf gohierf

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vnadot @gohierf