@clickview/ship-it 0.0.11 → 0.0.13

package/dist/X2/Objects.Api.md

@@ -1,30 +0,0 @@
-
-# Code changes
-- Update `ClickViewContentHandler` virtual assoc handler to use the master service `IsClickViewContentAsync`
-
-- Add `IsPublicUserContext` checks to all update object checks to prevent public users from updating objects
-
-- Add `IsPublicUserContext` checks to all create checks to prevent public users from creating objects
-
-- Don't add to a reference of the video result list in `VideoService`. Return a list instead
-
-- Ensure all assoc checks do not allow public access
-  - Almost all of these didn't however I've added a public check to short circuit a lot of them to avoid extra processing
-
-* Added unit tests for `AccessService` methods. Implements CORE-876
-
-
-# Testing
-- `IsClickViewContent` virtual assoc should be correct
-
-- Basic smoke test of updating objects
-- You should not be able to update any object with a public user context
-
-- Basic smoke test of creating objects
-- You should not be able to create any object with a public user context
-
-
-- You should not be allowed to associate any objects to another when using a public user context
-
-* All unit tests for `AccessService` should pass
-

package/dist/X2/Permissions.Api.md

@@ -1,34 +0,0 @@
-
-# Before release
-* Add `urls:domainApi` to Octo
-
-
-# Dependencies
-- https://gitlab.cvinternal.net/clickview/back-end/Master.Auth/-/merge_requests/308
-
-
-# Code changes
-- Add `/v1/users/permissions` to replace `/v1/users/{userId}/permissions`
-  - `UserId` is now optional, and if not specified will return permissions for a public user
-  - The public user logic uses the permission set "public"
-- Renamed `MasterPermissionSetRepository` to `InMemoryPermissionSetRepository`
-- Fixed sql error in `PermissionRepository.GetAllForSetAsync`
-
-- Moved fluent validation handling logic to a `ValidatorPipeline` for MediatR. This fixes an issue that was preventing the permission create and update endpoints from being hit. @prad.nepal Updated `FluentValidation.AspNetCore` from `9.2.0` to `11.2.2` in W3, in this upgrade the warnings that were previously thrown about the async validation turned into exceptions. See https://docs.fluentvalidation.net/en/latest/async.html.
-
-- Create `v1/access-policies/*` for access policy management
-- Create `GET/POST/DELETE v1/customers/{customerId}/access-policies` for customer access policy management
-- Create `AccessPolicyWorker` to move customers between policies on a schedule
-- Create `AccessPolicyBehaviour` to filter a user's permissions based on their access policy
-    - Filtering only occurs when the new `customerId` query parameter is used on the `v1/users/permissions` and `v1/users/{userId}/permissions` endpoints
-- Set `JsonIgnoreCondition.WhenWritingNull` so that null values are ignored
-
-
-# Testing
-- Getting permissions for a user will return
-- Getting permissions without a userId will return the public permissions
-
-- Creating a permission with an unknown permission set should show the validation error "Unknown permission set" 
-
-- N/A
-