[](https://pangea.cloud/docs/sdk/js/)
[](https://l.pangea.cloud/Jd4wlGs)
## Motivation
The Store Viewer can be used to search, view, and upload files or folders to your Pangea Secure Object Store.
An application using the Secure Object Store may also require that files are presented in the end application, because of this we made the file viewer React component that Pangea uses within its Console available as an NPM package, such that it could be embedded directly into other applications. The primary prop required is an API interface, which should contain callback handlers that handle making API requests to a server which proxies the Secure Object Store APIs. A proxy server is required because the service token from Pangea should not be embedded within a client.
The StoreFileViewer component is a React component built using the Material-UI (MUI) component library. MUI was used because it is the same component used within the Pangea Console.
## Getting Started
Install Material-UI library and the AuditLogViewer NPM package.
#### npm
```bash
npm install @mui/material @emotion/react @emotion/styled @pangeacyber/react-mui-store-file-viewer
```
#### yarn
```bash
yarn add @mui/material @emotion/react @emotion/styled @pangeacyber/react-mui-store-file-viewer
```
### Peer dependencies
Please note that react and react-dom are peer dependencies too:
```json
"peerDependencies": {
"react": "^17.0.0 || ^18.0.0",
"react-dom": "^17.0.0 || ^18.0.0"
},
```
To learn more about Material-UI (MUI) check out their official documentation(https://mui.com/material-ui/getting-started/installation/).
## StoreFileViewerProps Interface
### Description
The `StoreFileViewerProps` interface defines properties for configuring a file viewer component that interacts with a Secure Object Store service through the provided `StoreProxyApiRef`.
### Interface Definition
```typescript
interface StoreFileViewerProps {
children?: React.ReactNode;
apiRef: StoreProxyApiRef;
configurations?: StoreConfigurations;
defaultFilter?: ObjectStore.Filter;
defaultSort?: "asc" | "desc";
defaultSortBy?: keyof ObjectStore.ObjectResponse;
defaultVisibilityModel?: Record;
defaultColumnOrder?: string[];
customizations?: StoreDataGridCustomizations;
PangeaDataGridProps?: Partial<
PangeaDataGridProps
>;
}
```
### Props
- `children` (ReactNode, optional): Child components or elements.
- `apiRef` (StoreProxyApiRef, required): Reference to the store proxy API for communication with the object store.
- `configurations` (StoreConfigurations, optional): Configuration options for the file viewer.
- `defaultFilter` (ObjectStore.Filter, optional): Default filter to apply to the file viewer.
- `defaultSort` ("asc" | "desc", optional): Default sorting order for the file viewer.
- `defaultSortBy` (keyof ObjectStore.ObjectResponse, optional): Default property to sort the file viewer by.
- `defaultVisibilityModel` (Record, optional): Default visibility model for elements in the file viewer.
- `customizations` (StoreDataGridCustomizations, optional): Provide customization to rendered grid columns
- `defaultColumnOrder` (string[], optional): Default order of columns in the file viewer.
- `includeIdColumn` (boolean, optional): Toggle whether to include the object id as an new column. Defaulted to false;
- `PangeaDataGridProps` (Partial>, optional): Customization options for the internal PangeaDataGrid component used by the StoreFileViewer. From @pangeacyber/react-mui-shared.
## StoreProxyApiRef Interface
### Description
The `StoreProxyApiRef` interface defines methods and properties for interacting with a store proxy API. It includes functions for listing, getting, archiving, sharing, deleting, updating, uploading, and creating folders in the object store.
Only `list` and `get` are required to run the StoreFileViewer.
### Interface Definition
```typescript
interface StoreProxyApiRef {
list:
| ((
data: ObjectStore.ListRequest
) => Promise>)
| undefined;
get:
| ((
data: ObjectStore.GetRequest
) => Promise>)
| undefined;
getArchive?:
| ((
data: ObjectStore.GetArchiveRequest
) => Promise>)
| undefined;
share?: {
list?: (
data: ObjectStore.ListRequest
) => Promise>;
get?: (
data: ObjectStore.ShareGetRequest
) => Promise>;
delete?: (data: ObjectStore.ShareDeleteRequest) => Promise;
create?: (
data: ObjectStore.ShareCreateRequest
) => Promise>;
send?: (
data: ObjectStore.ShareSendRequest
) => Promise>;
};
delete?: (
data: ObjectStore.DeleteRequest
) => Promise>;
update?: (
data: ObjectStore.UpdateRequest
) => Promise>;
upload?: (
data: FormData,
contentType: "multipart/form-data"
) => Promise>;
folderCreate?: (
data: ObjectStore.FolderCreateRequest
) => Promise>;
}
```
For a deeper dive into the Prop interface check the source code [here](https://github.com/pangeacyber/pangea-javascript/blob/main/packages/react-mui-store-file-viewer/src/components/StoreFileViewer/index.tsx).
## Example
The following is brief example for how to initialize the AuditLogViewer component.
```jsx
import React from "react";
import {
StoreProxyApiRef,
StoreFileViewer,
} from "@pangeacyber/react-mui-store-file-viewer";
const storeCallbackHandler: StoreProxyApiRef = {
get: async (data) => {
const response = await api.storeGet(data);
return response;
},
list: async (data) => {
const response = await api.storeList(data);
return response;
},
};
const MyComponent: React.FC = () => {
return ;
};
```
## Customization
The StoreFileViewer component uses the Material-UI component library, so styling of the component can be controlled through a MUI Theme. See Theming documentation [here](https://mui.com/material-ui/customization/theming/)
What to apply your Pangea branding to your end application? Check out the `@pangeacyber/react-mui-branding` NPM package [here](https://github.com/pangeacyber/pangea-javascript/tree/main/packages/react-mui-branding). The BrandingThemeProvider can fetch your Pangea Projects Branding and apply the styling to a Material-UI Theme.
## API Reference
Store Service API's(https://pangea.cloud/docs/api/store)
## Development
First, run the development server:
```bash
yarn install
yarn storybook
```
The `StoreFileViewer.stories.tsx` storybook example does not use mock files to render the `StoreFileViewer` instead it will read a `.env` file to hit your Store Service Config.
Retrieve your Secure Object Store service token, client token and domain from the Pangea Console Store service dashboard and add the following to a `.env` file. The environment file is git ignored.
```env
STORYBOOK_PANGEA_TOKEN = "{SERVICE_TOKEN}"
STORYBOOK_CLIENT_TOKEN = "{CLIENT_TOKEN}"
STORYBOOK_SERVICE_DOMAIN = "{DOMAIN}"
```
Open [http://localhost:6060](http://localhost:6060) with your browser to view the component storybook