sap-samples / data-intelligence-pyoperator-generator Goto Github PK

The OSPO bot created this issue by mistake - It did not have enough priviledge to check the vulnerability alerts, So I am closing this issue now. Sorry for any inconvenience.

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-2
Explanation: Does it have an admin team on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-3
Explanation: Does it have enough admins on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

there is a small typo in the description of the readme - this issue did cost some time for me before I realized, that this was just a typo:

...
Usage: CLI call
yo di-operator [--init] [--overwrite]

his should be changed to:
yo di-pyoperator [--init] [--overwrite]

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-1
Explanation: Does it have enough teams on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-5
Explanation: Does teams have enough members on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-license_file-1
Explanation: Does it have a license file? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

The scaffolding code for the script "script.py" was not created when using the statement "yo di-pyoperator --init" but when using the statement "yo di-pyoperator --overwrite" additionally the scaffolding code was generated correctly.

If you only use the statement "yo di-pyoperator --overwrite" the "utils" Folder was missing, so in order to use the full functionality I had to run both statements:
first:
yo di-pyoperator --init
second - directy after the first statement.
yo di-pyoperator --overwrite