Applied commit on master (using cherry-pick)

Adds test for invalid value for a field.
If a list(or any other type) is provided where a string is expected, the field is simply ignored.

Sorry about the change. It was by mistake.

Squash commits

Adds test for empty fields in CFFMapping

Checks value types in normalize methods
Deletes the extra function added for type checking

Checks value types in normalize methods
Deletes the extra function added for type checking

I'm not so sure what needs to be done here.
If some fields have no values, does it have to skip it or put some default value?

Rebased

Tests cff mappings of empty yaml files
Tests cff mappings of lists in yaml files

Okay, got it. I have made these changes. Updated the diff title and is the summary of D8002 sufficient & correct now?

Changes commit message

In D8002#208133, @vlorentz wrote:

2. Please mention the task you are solving in the diff description (see https://docs.softwareheritage.org/devel/contributing/git-style-guide.html )

Do I repeat which task I am solving in every diff description?
If so, I suppose I am to put as the subject, what I am changing in the diff, eg. "rebase", "fix XXX" etc in the title of the diff. Is this right?

Undo a change not for T4276

Cleans commit history

Rebase

• Ignores invalid yaml files
• Solves hypothesis error in T4333

Undo deletion of normalize_description

Adds test for skipping invalid yaml files

Logs the invalid-yaml-file-warning

Logs warning of invalid yaml file

Oops... updated it :-)

Include vickymerzown in CONTRIBUTORS

Update title of D7823

I did some horrible things with git. after you accepted my diff, I merged my branch to master. When I tried pushing, it was throwing an error. Turns out that I made a few commits on master before I started working on the new branch. So I tried to squash these commits on master and I squashed a couple of commits that weren't mine, to begin with. Could you please suggest what to do? Right now, it would be easy to just make the changes in a new diff. is this okay?

• Reformat test to detect uppercase NPM metadata file
• Add vickymerzown to CONTRIBUTORS

• Add vickymerzown to CONTRIBUTORS

Parametrize test using subTest in unittest

Test using @pytest.mark.parametrize decorator

My pleasure... :-)

Squash all commits

• Revise annotations in base.py

Revise annotations of and Format codemeta.py and maven.py

• Revise changes to base.py WRT comments
• Revise annotatiions to cff.py

This looks really interesting to me. How exactly can I get started? Where is the web app present? (Isn't it hosted on Docker?)

Hello @arishmaurya , it is on the add-forge-now admin dashboard view but isn't open publicly yet (from @ardumont 's comment on https://forge.softwareheritage.org/T4078).

• Add annotations to maven.py

• Add annotations to codemeta.py

• Add some more annotations to base.py

Add annotations to __init__.py, base.py and cff.py

• Add some more annotations to base.py
• Add some more annotations to cff.py

• Add annotations to cff.py

In D7587#198105, @vlorentz wrote:

Add annotations to cff.py

Add annotations to base.py

Add annotations to base.py

Add annotations to base.py

@ardumont Is this good enough to be merged? If so, there are other annotations that need to be added and I'll create those diffs as well.

Add annotations to the functions in base.py

While annotating, are we expected to use native Python Datatypes (like str, int, float etc.) or do I use the NewType class of the Type library as in the example below:

Hey, I would like to work on this issue.

Sometimes these variants site side by side with the plain text ones

I didn't understand what site here means.
Could anyone help me with more info about the issue?