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

Add metadata documentation #2547

Merged
merged 13 commits into from
May 28, 2020
Merged

Add metadata documentation #2547

merged 13 commits into from
May 28, 2020

Conversation

Markel
Copy link
Contributor

@Markel Markel commented Apr 27, 2020

I found out that there was no documentation for the metadata of the files, so I created a little Markdown file explaining what every piece of metadata represents + putting all of them together, as all the detects don't have the same amount of metadata.

I didn't know where to put this information, so I created a new file, feel free to suggest any other location.

There is also some of them that I don't know their functionality, I'll comment them on line comments.

metadata.md Outdated Show resolved Hide resolved
metadata.md Outdated Show resolved Hide resolved
@Markel Markel requested a review from patrickkettner April 27, 2020 18:40
metadata.md Outdated Show resolved Hide resolved
metadata.md Outdated Show resolved Hide resolved
metadata.md Outdated Show resolved Hide resolved
metadata.md Outdated Show resolved Hide resolved
metadata.md Outdated Show resolved Hide resolved
Copy link
Member

@rejas rejas left a comment

Choose a reason for hiding this comment

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

lgtm!

@rejas
Copy link
Member

rejas commented Apr 28, 2020

but why not put this info into the README or in a doc named "how to write tests" (working title)
here in metadata.md it just sits around with no obvious purpose from the outside...

@Markel
Copy link
Contributor Author

Markel commented Apr 28, 2020

I didn't know where to put this information, so I created a new file,

I like more the idea of the "how to write tests" as I find that the README would get too big if we include the entire schema + table. Additionally, the information of this file is more technicalities than a general purpose read that a README represents.

But yes, even knowing of the existence of the file it was hard to find in the explorer, so a rename would be nice 😅.

@patrickkettner
Copy link
Member

I find that the README would get too big

+1.

@rejas
Copy link
Member

rejas commented Apr 28, 2020

Then rename it to HOW_TO_WRITE_FEATURE_DETECTS.md :-)

Also changed the header levels to accomodate the new title/purpose
@Markel
Copy link
Contributor Author

Markel commented Apr 28, 2020

Done, I also changed the header levels, because the title implies that in some day there will be other subjects apart from metadata

@patrickkettner
Copy link
Member

is the doc going to be updated to be about how to write feature detects, then? it doesn't really mention that at all...

@Markel
Copy link
Contributor Author

Markel commented Apr 28, 2020

Okay, I'll add some title and description later in the day, writing Markdown in mobile would be horrible 😅

@patrickkettner
Copy link
Member

thanks @MarkelFe!!

@Markel
Copy link
Contributor Author

Markel commented Apr 28, 2020

I made it a little vague because I'm not entirely sure which kind of information could go in this file, once it grows the statement could probably be more precise.

I've based the table of contents style from the atom contributing guidelines. Also, sorry for the commit mess, I had just configured my GPG key on git and vscode and one commit went with the wrong email address.

@rejas rejas self-requested a review April 28, 2020 18:35
Copy link
Member

@rejas rejas left a comment

Choose a reason for hiding this comment

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

lgtm! thx for the work!

@codecov
Copy link

codecov bot commented May 5, 2020

Codecov Report

❗ No coverage uploaded for pull request base (master@1baf805). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #2547   +/-   ##
=========================================
  Coverage          ?   95.15%           
=========================================
  Files             ?        5           
  Lines             ?      165           
  Branches          ?        0           
=========================================
  Hits              ?      157           
  Misses            ?        8           
  Partials          ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1baf805...610fbbc. Read the comment docs.

@Markel
Copy link
Contributor Author

Markel commented May 7, 2020

@patrickkettner everything right with the PR?

@Markel Markel mentioned this pull request May 13, 2020
@rejas
Copy link
Member

rejas commented May 26, 2020

Last chance for @patrickkettner to object before I merge it tomorrow :-)

@rejas rejas merged commit bd28403 into Modernizr:master May 28, 2020
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.

3 participants