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.

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

Document that YAML files are expected to be in YAML1.2 #1764

Merged
merged 6 commits into from
Oct 19, 2020

Conversation

skshetry
Copy link
Member

@skshetry skshetry commented Sep 8, 2020

Refer iterative/dvc#4415

Fixes #1704

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.

🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.

Please choose to allow us to edit your branch when creating the PR.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

@skshetry skshetry self-assigned this Sep 8, 2020
@shcheklein shcheklein temporarily deployed to dvc-landing-skshetry-ya-q7tcgk September 8, 2020 10:34 Inactive
Copy link
Member

@shcheklein shcheklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great overall, I would avoid using notes though

@shcheklein shcheklein temporarily deployed to dvc-landing-skshetry-ya-q7tcgk September 10, 2020 07:10 Inactive
@shcheklein

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

Comment on lines 27 to 29
YAML, JSON, or TOML _parameters file_. Multiple parameter dependencies can be
specified from one or more parameters files.
YAML (specifically in YAML 1.2 format), JSON, or TOML _parameters file_.
Multiple parameter dependencies can be specified from one or more parameters
files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same, just "YAML 1.2"? (Linked)

Copy link
Contributor

@jorgeorpinel jorgeorpinel Sep 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, there's several other files that include this params file formats list. Please see #1799 (review)

Copy link
Contributor

@jorgeorpinel jorgeorpinel Sep 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • In fact I'd just grep YAML (upper case and double check all instances (there's 28). DONE SEPARATELY

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not change everywhere, it's enough to mention it in key areas. It's still YAML, so it's fine.

Copy link
Contributor

@jorgeorpinel jorgeorpinel Oct 9, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, just Same, just "YAML 1.2" please.

it's enough to mention it in key areas

OK but why are the metrics/params index more important than docs/start/experiments or docs/user-guide/basic-concepts/parameter? (or other places)

Copy link
Contributor

@jorgeorpinel jorgeorpinel Oct 9, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact I'd just grep YAML (upper case and double check all instances

I didn't mean change it everywhere BTW, but we need to check all 28 instances please, and decide which ones to change. I think it should definitely be more than just this one

It's a simple change from YAML to "YAML 1.2".

Copy link
Contributor

@jorgeorpinel jorgeorpinel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @skshetry ! Left some specific comments above ☝️

p.s. I can polish the language if needed in the next round.

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Sep 23, 2020

Also, questions/requests:

@skshetry

This comment has been minimized.

@skshetry
Copy link
Member Author

skshetry commented Oct 5, 2020

Same Q for the note "The workaround will be to add YAML version directive...

The workaround no longer works, so it's YAML1.2 for now.

@jorgeorpinel jorgeorpinel mentioned this pull request Oct 9, 2020
20 tasks
Copy link
Contributor

@jorgeorpinel jorgeorpinel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the answers @skshetry. No changes still, please see the open discussions above. Thanks!

skshetry and others added 2 commits October 19, 2020 01:47
Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com>
@shcheklein shcheklein merged commit 73ba3cf into master Oct 19, 2020
@shcheklein
Copy link
Member

Merged. It's not that important change to do many iterations to my mind.

@skshetry skshetry deleted the skshetry/yaml-1-2 branch December 9, 2020 02:53
@jorgeorpinel jorgeorpinel mentioned this pull request Dec 22, 2020
12 tasks
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.

Document that yaml files are expected to be in YAML v1.2
4 participants