refactor: introduce abstractions at the workspace level #3836
Commits on May 22, 2024
-
Co-authored-by: Andrew Bastin <andrewbastin.k@gmail.com>
-
-
refactor: compile data in handles
Introduce a handle for requests.
-
-
-
refactor: save request handle in tabs and remove tabs related logic f…
…rom personal provider definition
-
refactor: persist request handle under tab saveContext
Bump vue version.
-
-
-
refactor: port collection tree rendered in the save request modal to …
…the new implementation
-
-
fix: updates to collection level authorization and headers reflect at…
… the request level straightaway
-
-
-
-
-
-
refactor: remove fields associated with pagination
Fix lint errors
-
-
-
-
-
-
-
-
refactor: eliminate
collectionIDfrom tabsaveContextCollection ID can be inferred from request ID by removing last index from the path.
-
refactor: eliminate
parentCollectionIDfield from `RESTCollectionVi……ewRequest` type Collection ID serves the purpose.
-
-
fix: ensure the collection tree for search immediately reflects actio…
…ns performed over it
-
-
fix: duplicate collection in search results
Ensure the entire collection tree is rendered if the search query matches a collection name.
-
-
-
-
-
-
refactor: persist request handles under tab
saveContextOnly the IDs (workspace, provider & request IDs) to restore the handle are stored under `localStorage` and the handle is restored back at runtime.
-
refactor: introduce writable handles to signify updates to handle ref…
…erences A special list of writable handles is compiled in a list while issuing handles (request/collection creation, etc). Instead of manually computing the tab and toggling the dirty state, the writable handle is updated (changing the type to invalid on request deletion) and the tab with the request open can infer it via the update reflected in the request handle under the tab save context (reactive update trigger).
-
-
fix: make writable handle operate on refs within the `createRESTReque…
…st` method Wrap the request handle data in a `ref` and make the writable handle operate over it ensuring reactive updates are received.
-
refactor: consider request handles with tab saveContext resolution fo…
…r collection move/reorder actions
-
refactor: move tab saveContext resolution associated with actions on …
…collections to be based on request handles
-
refactor: persist only request handles under tab
saveContextat run……time Remove provider, workspace and request IDs.
-
refactor: better tab dirty check
Mark the tab (saved request under a collection) as not dirty if the request contents are reset to the value since previous save.
-
refactor: handle updates post move request action
- Filter out duplicate issued handle entries. - Move from `getAffectedIndexes` helper function to a custom implementation for updating affected request indices.
-
-
-
-
-
-
-
fix: handle based updates post collection move to a sibling level col…
…lection below it
-
fix: empty state primary action for root collections
Ensure child collections are created instead of the action resulting in new root collections.
-
fix: resolve edge cases about moving collections under its sibling
- Increase test coverage. - Move store mock data under `__tests__/__mocks__`. - Rephrase test descriptions.
Commits on May 27, 2024
-
refactor: update
exportRESTCollectionsmethod signature- Drop the `collections` parameter since the it is already available in the `PersonalWorkspaceProviderService` context. - Make the above method return a left error of `NO_COLLECTIONS_TO_EXPORT` when the collections list is empty. - Error handling updates.