spdx-online-tools
spdx-online-tools copied to clipboard
spdx
Source for the website providing online SPDX tools
The test_archive_license_requests_feature unit test is failing on the current master branch: ``` ====================================================================== ERROR: test_archive_license_requests_feature (app.tests.ArchiveLicenseRequestsViewsTestCase) Check if the license is shifted to archive requests when archive button is pressed...
The following test_post_submit unit test fails on the master branch: ``` ====================================================================== FAIL: test_post_submit (app.tests.SubmitNewLicenseViewsTestCase) POST Request for submit a new license ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/runner/work/spdx-online-tools/spdx-online-tools/src/app/tests.py",...
When using the "License XML Editor" "Submit Changes" feature, if the user's fork of the license-list-XML repo is not named precisely `license-list-XML`, the submission will fail with a very generic...
Linters are tools that help identify and report errors in code, helping to ensure that the codebase is of a high quality and follows best practices. The SPDX Online Tools...
- Try to address issue #453 to make the Tool more convenient to the users. - Added GitHub issue id to the Request model. - Access it in the `license_information.html`
- Logged in with the user setup in secrets.py - Add client `sessionid` to selenium driver - Mocked the app.utils.checkPermission to return true When the `app.utils.checkPermission` returns true, `context_dict['authorized']` becomes...
@rtgdk I have added a swagger point and it contains all the API endpoints as the first step of #91. Need suggestions.
As seen in https://github.com/spdx/license-list-XML/issues/1414, license **namespace** requests produce GitHub issues which are indistinguishable from those made by normal license requests. The generated GitHub issues should specify that the request is...
Although, the wiki [here](https://github.com/spdx/spdx-online-tools/wiki/REST-API-Fields-Request-and-Response) is enough to interact with the API but adding a support for [API documentation](https://www.django-rest-framework.org/topics/documenting-your-api) will help people new to the repo, understand what the API can...
Some tests need to done to ensure proper workflow of the the website. Refer to #149 for example.
