This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: ZeroTwentyFifty/pathfinder_network
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Go back through the Assurance datatype and make it more consistent
#27
opened May 1, 2023 by
JohnVonNeumann
The solution implements asynchronous requests / retrieval of ProductFootprints through the Events action, in accordance with the Technical Specifications
conformance-optional
Optional functionality for meeting conformance testing requirements.
The solution can be notified of updates to a ProductFootprint through the Events action, in accordance with the Technical Specifications
conformance-optional
Optional functionality for meeting conformance testing requirements.
The ListFootprints action implements the possibility of getting partial results (HTTP code 202)
conformance-optional
Optional functionality for meeting conformance testing requirements.
The ListFootprints action implements the filter option
conformance-optional
Optional functionality for meeting conformance testing requirements.
The solution implements Product Lifecycle events and rules in accordance with the Technical Specifications
conformance-optional
Optional functionality for meeting conformance testing requirements.
The solution either implements the § 3.2.1 Events action or responds to authenticated Events calls with the NotImplemented error code
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution implements the § 3.3 Error Responses described above (in accordance with the Technical Specification)
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution’s endpoints follow the request/response syntax described above (in accordance with the Technical Specification)
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution performs the authentication flow described in the Technical Specification
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
All endpoints use HTTPS
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The ListFootprints action implements mandatory server-side pagination, in accordance with the Technical Specification
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution implements the § 3.1.3 GetFootprint action
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution implements the 3.1.2 ListFootprints action
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
The solution implements the 3.1.1 Authenticate action
conformance-mandatory
Mandatory functionality for meeting conformance testing requirements.
Fix/remove flake8 and replace with pylint or something better.
#4
opened Apr 20, 2023 by
JohnVonNeumann
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.