Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

241 dca 5 create the content upload and editing interface #269

Merged

Conversation

sebpalluel
Copy link
Contributor

@sebpalluel sebpalluel commented Feb 2, 2024

Type

Enhancement


Description

  • Added a new component ContentSpaceFilesTableClient to display a table of files for a content space. The table includes functionalities such as file selection, file actions (show, download, delete), and batch actions for selected files

Changes walkthrough

Relevant files
New feature
ContentSpaceFilesTableClient.tsx
Added ContentSpaceFilesTableClient component                                         

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTableClient.tsx

  • Created a new file ContentSpaceFilesTableClient.tsx which is a
    component to display a table of files for a content space.
  • The table includes functionalities such as file selection, file
    actions (show, download, delete), and batch actions for selected files.
+196/-0 
ContentSpaceFilesUploaderClient.tsx
Added ContentSpaceFilesUploaderClient component                                   

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesUploader/ContentSpaceFilesUploaderClient.tsx

  • Created a new file ContentSpaceFilesUploaderClient.tsx which is a
    component to upload files for a content space.
+114/-0 
Enhancement
index.ts
Updated GraphQL query types                                                                           

libs/gql/admin/types/src/generated/index.ts

  • Updated the GetContentSpaceWithPassesOrganizerQuery and
    GetEventWithPassesOrganizerQuery types to include the id field and
    eventParameters.status field respectively.
+2/-2     
Documentation
ContentSpaceFilesTable.stories.tsx
Added Storybook story for ContentSpaceFilesTable component             

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTable.stories.tsx

  • Created a new Storybook story for the ContentSpaceFilesTable
    component.
+104/-0 
Tests
deleteContentSpaceFiles.spec.ts
Added unit tests for deleteContentSpaceFiles action                           

libs/features/back-office/content-spaces/src/lib/actions/deleteContentSpaceFiles.spec.ts

  • Added unit tests for the deleteContentSpaceFiles action.
+104/-0 

✨ Usage guide:

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...
Enabling\disabling automation
  • When you first install the app, the default mode for the describe tool is:
pr_commands = ["/describe --pr_description.add_original_user_description=true" 
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

  • Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:
pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

  • type: the PR type.
  • summary: the PR summary.
  • walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].

If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

  • Main topic:performance - pr_agent:The main topic of this PR is performance
  • New endpoint - pr_agent:A new endpoint was added in this PR
  • SQL query - pr_agent:A new SQL query was added in this PR
  • Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
  • ...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Inline File Walkthrough 💎

For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).

To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

  • 'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
  • true: A collapsable file comment with changes title and a changes summary for each file in the PR.
  • false (default): File changes walkthrough will be added only to the "Conversation" tab.
Utilizing extra instructions

The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.

Examples for extra instructions:

[pr_description] 
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

Copy link

vercel bot commented Feb 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
back-office ❌ Failed (Inspect) Feb 5, 2024 10:20am
marketplace ❌ Failed (Inspect) Feb 5, 2024 10:20am

@codiumai-pr-agent-free codiumai-pr-agent-free bot added the enhancement New feature or request label Feb 2, 2024
Copy link

PR Description updated to latest commit (5f2aa14)

Copy link

PR Analysis

  • 🎯 Main theme: Adding a content upload and editing interface
  • 📝 PR summary: This PR introduces a new component for displaying a table of files for a content space. The table includes functionalities such as file selection, file actions (show, download, delete), and batch actions for selected files. It also includes tests for the new features.
  • 📌 Type of PR: Enhancement
  • 🧪 Relevant tests added: Yes
  • ⏱️ Estimated effort to review [1-5]: 4, because the PR is quite large and introduces a new feature with several functionalities. It also includes changes in multiple files, which increases the complexity of the review.
  • 🔒 Security concerns: No

PR Feedback

💡 General suggestions: The code looks well-structured and follows good practices. However, there are several TODO comments in the code where actions for file operations should be implemented. It's recommended to either implement these actions or, if they are planned for future PRs, provide more context in the comments about when and how these actions will be implemented.


✨ Usage guide:

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...
Utilizing extra instructions

The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.

Examples for extra instructions:

[pr_reviewer] # /review #
extra_instructions="""
In the 'general suggestions' section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation
  • When you first install PR-Agent app, the default mode for the review tool is:
pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels

The review tool can auto-generate two specific types of labels for a PR:

  • a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
  • a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)
Extra sub-tools

The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_ticket, and more.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

Copy link

PR Code Suggestions

Suggestions                                                                                                                                                         
enhancement
Extract the checkbox component into a separate reusable component.           

Extract the checkbox component into a separate reusable component.

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTableClient.tsx [50-65]

-50 +      header: ({ table }) => (
-51 +        <Checkbox
-52 +          checked={table.getIsAllPageRowsSelected()}
-53 +          onCheckedChange={(value) => table.toggleAllPageRowsSelected(!!value)}
-54 +          aria-label="Select all"
-55 +          className="translate-y-[2px]"
-56 +        />
-57 +      ),
-58 +      cell: ({ row }) => (
-59 +        <Checkbox
-60 +          checked={row.getIsSelected()}
-61 +          onCheckedChange={(value) => row.toggleSelected(!!value)}
-62 +          aria-label="Select row"
-63 +          className="translate-y-[2px]"
-64 +        />
-65 +      ),
+50 +      header: ({ table }) => <CheckboxHeader table={table} />,
+51 +      cell: ({ row }) => <CheckboxCell row={row} />,
 
Extract the ContentSpaceFilesUploader component into a separate reusable component.

Extract the ContentSpaceFilesUploader component into a separate reusable component.

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTableClient.tsx [189-192]

-189 +        <ContentSpaceFilesUploader
+189 +        <ContentSpaceFilesUploaderComponent
 190 +          organizerId={organizerId}
 191 +          contentSpaceId={contentSpaceId}
 192 +        />
 
Add a status badge to the event title                                        

Add a status badge to the event title

libs/features/back-office/events/src/lib/organisms/EventSheet/EventSheet.tsx [22-27]

 export const EventSheet = ({ event, organizerId }: EventSheetProps) => {
   return (
     <>
       <SheetHeader size="full">
         <SheetTitle className="flex items-baseline space-x-2">
           <span>{event.title}</span>
+          <EventStatusBadge status={event.eventParameters?.status} />
         </SheetTitle>
       </SheetHeader>
       <SheetOverflow className="grid h-full gap-8 py-3 pb-28 md:grid-cols-2">
         {event.eventPasses?.map((eventPass, index) => (
 
best practice
Use destructuring assignment for props in the ContentSpaceFilesTableClient component.

Use destructuring assignment for props in the ContentSpaceFilesTableClient component.

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTableClient.tsx [26-30]

 26 +  extends Omit<DataTableProps<ContentSpaceFileWithName, unknown>, 'columns'>,
-27 +    GetContentSpaceFolderPath {
-28 +  headerControlText: DataTableColumnHeaderProps<any, any>['controlText'];
-29 +}
+27 +    GetContentSpaceFolderPath,
+28 +    {
+29 +      headerControlText: DataTableColumnHeaderProps<any, any>['controlText'];
+30 +    }
 
Use the 'key' prop when rendering the DataTableRowActions component.         

Use the 'key' prop when rendering the DataTableRowActions component.

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/ContentSpaceFilesTableClient.tsx [128]

-128 +        return <DataTableRowActions items={items} />;
+128 +        return <DataTableRowActions key={row.id} items={items} />;
 
Remove unused imports in ContentSpaceFilesUploaderClient.tsx                 

Remove unused imports

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesUploader/ContentSpaceFilesUploaderClient.tsx [2-11]

-+import * as Bytescale from '@bytescale/sdk';
-+import {
-+  UploadDropzone,
-+  UploadDropzoneConfig,
-+} from '@bytescale/upload-widget-react';
-+import env from '@env/client';
-+import {
-+  getContentSpaceFolderPath,
-+  type GetContentSpaceFolderPath,
-+} from '@features/content-space-common';
++import { UploadDropzone, UploadDropzoneConfig } from '@bytescale/upload-widget-react';
++import { getContentSpaceFolderPath, type GetContentSpaceFolderPath } from '@features/content-space-common';
 +import { useUploader } from '@next/uploader-provider';
 +import { useEffect } from 'react';
 
Remove commented code in ContentSpaceFilesUploaderClient.tsx                 

Remove commented code

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesUploader/ContentSpaceFilesUploaderClient.tsx [35-62]

 +    // locale: {
 +    //   //TODO add translations
 +    // },
-+    // onPreUpload: (file: File) => {
-+    //   return new Promise<UploadWidgetOnPreUploadResult | undefined>(
-+    //     (resolve, reject) => {
-+    //       getEventPassFileCount({
-+    //         organizerId,
-+    //         eventId,
-+    //         eventPassId,
-+    //       })
-+    //         .then((numFiles) => {
-+    //           console.log('numFiles', numFiles);
-+    //           resolve({
-+    //             transformedFile: new File(
-+    //               [file],
-+    //               `${eventId}-${eventPassId}-${numFiles}.png`,
-+    //               {
-+    //                 type: file.type,
-+    //                 lastModified: file.lastModified,
-+    //               },
-+    //             ),
-+    //           });
-+    //         })
-+    //         .catch(reject);
-+    //     },
-+    //   );
-+    // },
 
Remove unused imports in ContentSpaceSheet.tsx                               

Remove unused imports

libs/features/back-office/content-spaces/src/lib/pages/ContentSpaceSheet/ContentSpaceSheet.tsx [1-12]

-+import {
-+  Accordion,
-+  AccordionContent,
-+  AccordionItem,
-+  AccordionTrigger,
-+  SheetHeader,
-+  SheetNavigation,
-+  SheetNavigationSkeleton,
-+  SheetOverflow,
-+  SheetTitle,
-+  SheetTitleSkeleton,
-+} from '@ui/components';
++import { Accordion, AccordionContent, AccordionItem, AccordionTrigger, SheetHeader, SheetNavigation, SheetOverflow, SheetTitle } from '@ui/components';
 +import { useLocale, useTranslations } from 'next-intl';
 +import Link from 'next/link';
 +import { ContentSpaceStatusBadge } from '../../atoms/ContentSpaceStatusBadge/ContentSpaceStatusBadge';
 +import { ContentSpaceEventPassesTable } from '../../organisms/ContentSpaceEventPassesTable/ContentSpaceEventPassesTable';
-+import {
-+  ContentSpaceNftFiles,
-+  ContentSpaceNftFilesProps,
-+} from '../../organisms/ContentSpaceFiles/ContentSpaceFiles';
-+// import {
-+//   EventPassCard,
-+//   EventPassCardSkeleton,
-+//   type EventPassCardProps,
-+// } from '../EventPassCard/EventPassCard';
++import { ContentSpaceNftFiles, ContentSpaceNftFilesProps } from '../../organisms/ContentSpaceFiles/ContentSpaceFiles';
 
Remove unused imports in ContentSpaceFilesUploader.tsx                       

Remove unused imports

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesUploader/ContentSpaceFilesUploader.tsx [1-14]

-+import { UploaderProvider } from '@next/uploader-provider';
-+import {
-+  Button,
-+  ButtonSkeleton,
-+  Dialog,
-+  DialogClose,
-+  DialogContent,
-+  DialogFooter,
-+  DialogHeader,
-+  DialogTitle,
-+  DialogTrigger,
-+  HelperText,
-+} from '@ui/components';
++import { Button, Dialog, DialogClose, DialogContent, DialogFooter, DialogHeader, DialogTitle, DialogTrigger, HelperText } from '@ui/components';
 +import { Upload } from '@ui/icons';
 +import { useLocale } from 'next-intl';
 +import { getTranslations } from 'next-intl/server';
 +import { Suspense } from 'react';
 +import { getContentSpaceFiles } from '../../actions/getContentSpaceFiles';
-+import {
-+  ContentSpaceFilesClientProps,
-+  ContentSpaceFilesUploaderClient,
-+} from './ContentSpaceFilesUploaderClient';
++import { ContentSpaceFilesClientProps, ContentSpaceFilesUploaderClient } from './ContentSpaceFilesUploaderClient';
 
Remove unused imports in examples.tsx                                        

Remove unused imports

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFilesTable/examples.tsx [1-6]

-+import * as authProvider from '@next/auth';
-+import * as uploaderProvider from '@next/uploader-provider';
-+import { i18nUiTablesServerMocks } from '@test-utils/ui-mocks';
-+import { sleep } from '@utils';
-+import * as nextIntl from 'next-intl';
 +import { createMock } from 'storybook-addon-module-mock';
 +import * as deleteFile from '../../actions/deleteContentSpaceFile';
 +import * as getPass from '../../actions/getContentSpaceFiles';
 
maintainability
Remove unused imports                                                        

Remove unused imports

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpaceFiles/ContentSpaceFiles.tsx [1-8]

 import { NextIntlClientProvider, useLocale, useTranslations } from 'next-intl';
 import { Suspense } from 'react';
 import { ContentSpaceFromOrganizerWithPasses } from '@features/back-office/content-spaces-types';
 import { Locale, messages } from '@next/i18n';
 import { deepPick } from '@utils';
 import { ContentSpaceFilesUploader } from '../ContentSpaceFilesUploader/ContentSpaceFilesUploader';
+import { TableSkeleton } from '@ui/components';
 
Remove unused imports                                                        

Remove unused imports

libs/features/back-office/events/src/lib/organisms/EventSheet/EventSheet.stories.tsx [13-16]

 import { mobileMode } from '@test-utils/storybook';
 import { getMock, render } from 'storybook-addon-module-mock';
 import { eventWithNormalPasses } from './examples';
+import { EventStatus_Enum } from '@gql/shared/types';
 
Remove unused import                                                         

Remove unused import

libs/features/back-office/events/src/lib/molecules/EventPassNftFilesTable/EventPassNftFilesTableClient.tsx [13]

-import { ColumnsProps } from '../../organisms/EventsTable/EventsTable';
+import { GetEventPassOrganizerFolderPath } from '../../organisms/EventsTable/EventsTable';
 
Remove unused import for ContentSpaceStatusBadge                

Remove unused import for ContentSpaceStatusBadge

libs/features/back-office/content-spaces/src/lib/organisms/ContentSpacesTable/ContentSpacesTable.tsx [18]

-import { ContentSpaceStatusBadge } from '../../atoms/ContentSpaceStatusBadge/ContentSpaceStatusBadge';
+...
 

✨ Usage guide:

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...
Enabling\disabling automation

When you first install the app, the default mode for the improve tool is:

pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...]

meaning the improve tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically.

Utilizing extra instructions

Extra instructions are very important for the improve tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on.

Examples for extra instructions:

[pr_code_suggestions] # /improve #
extra_instructions="""
Emphasize the following aspects:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

A note on code suggestions quality
  • While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically.
  • Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base.
  • Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the custom suggestions 💎 tool
  • With large PRs, best quality will be obtained by using 'improve --extended' mode.
More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the improve usage page for a more comprehensive guide on using this tool.

…types to fix compilation error

🔧 chore(EventSheet.stories.tsx): update event prop to include eventParameters.status to fix test expectations
🔧 chore(EventSheet.tsx): import EventStatusBadge component to display event status
🔧 chore(EventSheet.tsx): update SheetTitle component to include EventStatusBadge component
🔧 chore(event.query.gql): add eventParameters.status field to query to fetch event status

🚀 feat(ContentSpaceStatusBadge): add ContentSpaceStatusBadge component to display the status of a content space
🔄 refactor(ContentSpacesTable): update import path for ContentSpaceStatusBadge component to reflect its new location in the atoms folder

🔧 chore(content-spaces-types): add types for GetContentSpaceWithPassesOrganizerQuery and ContentSpaceFromOrganizerWithPasses to improve type safety

🆕 feat(ContentSpaceEventPassesTable.tsx): add new component ContentSpaceEventPassesTable to display event passes for a content space

🆕 feat(ContentSpaceFiles.tsx): add new component EventPassNftFiles to display NFT files for an event pass

🆕 feat(ContentSpaceSheet.tsx): add new component ContentSpaceSheet to display content space details and event passes

🆕 feat(pass-common): add getContentSpaceFolderPath function to generate the folder path for a content space

🔧 chore(contentSpace.query.gql): remove heroImage field from GetContentSpaceWithPassesOrganizer query as it is not used

🔨 refactor(page.tsx): remove unused imports and commented out code
🔨 refactor(index.ts): update import path for ContentSpacesPage component
🔨 refactor(ContentSpaceFiles.tsx): update import path for ContentSpaceNftFilesTable component
🔨 refactor(ContentSpaceSheet.tsx): update import paths for components and remove commented out code
✨ feat(ContentSpaceSheet.tsx): create ContentSpaceSheet component to display content space details and files
✨ feat(ContentSpacesPage.tsx): create ContentSpacesPage component to display a table of content spaces

📦 chore(content-spaces): add examples file for ContentSpaceEventPassesTable component
📦 chore(content-spaces): add ContentSpaceSheet component and its stories
🐛 fix(content-spaces): update translation key for go-back button in ContentSpaceSheet component
📦 chore(content-spaces): add examples file for ContentSpaceSheet component
🌐 feat(i18n): add translation for go-back button in ContentSpaceSheet component

🚀 feat(ContentSpaceSheet.tsx): add Accordion component to display associated event passes and files in ContentSpaceSheet
🌐 feat(en.json): add translation for "Associated Event Passes" in Sheet section

🔧 fix(content-space-common): remove unused code and export getContentSpaceFolderPath function
🔧 fix(gql): add id field to GetContentSpaceWithPassesOrganizer query to retrieve content space id

🔧 fix(deleteContentSpaceFile.spec.ts): fix import statement for FileWrapper and revalidateTag
✨ feat(deleteContentSpaceFile.ts): add deleteContentSpaceFile function to delete a file from a content space and revalidate cache
🔧 fix(deleteContentSpaceFiles.spec.ts): fix import statement for FileWrapper and revalidateTag
✨ feat(deleteContentSpaceFiles.ts): add deleteContentSpaceFiles function to delete multiple files from a content space and revalidate cache
✨ feat(getContentSpaceFiles.tsx): add getContentSpaceFiles function to get a list of files in a content space

🐛 fix(ContentSpaceEventPassesTable.tsx): remove unused import and fix indentation
✨ feat(ContentSpaceEventPassesTable.tsx): add support for translations using next-intl library to improve internationalization
🐛 fix(ContentSpaceFiles.tsx): remove unused import and fix indentation
✨ feat(ContentSpaceFiles.tsx): add ContentSpaceFilesUploader component to allow users to upload files to content space
✨ feat(ContentSpaceFilesTable.stories.tsx): create a new story file for ContentSpaceFilesTable component
✨ feat(ContentSpaceFilesTable.tsx): create ContentSpaceFilesTable component to display a table of content space files
✨ feat(ContentSpaceFilesTableClient.tsx): create ContentSpaceFilesTableClient component to render the content space files table using DataTable component
✨ feat(ContentSpaceFilesTableClient.tsx): add support for row selection and menu actions in the content space files table
✨ feat(ContentSpaceFilesTableClient.tsx): add ContentSpaceFilesUploader component to allow users to upload files to content space
✨ feat(ContentSpaceFilesTableClient.tsx): add support for deleting files from content space
✨ feat(ContentSpaceFilesTable/examples.tsx): create mocks for getContentSpaceFiles and deleteContentSpaceFile functions to be used in storybook examples

🚀 feat(ContentSpaceFilesUploader): add ContentSpaceFilesUploader component to allow users to upload files to a content space
🚀 feat(ContentSpaceFilesUploader): add support for displaying a loading skeleton while uploader session is not ready
🚀 feat(ContentSpaceFilesUploader): add support for fetching current files in the content space and displaying them in the uploader
🚀 feat(ContentSpaceFilesUploader): add support for uploading image files to the content space using the Bytescale upload widget
🚀 feat(ContentSpaceFilesUploader): add support for displaying a dialog with the uploader when the upload button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for closing the dialog when the close button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for showing a helper text with disabled reasons
🚀 feat(ContentSpaceFilesUploader): add support for showing a loading skeleton while uploader session is not ready
🚀 feat(ContentSpaceFilesUploader): add support for fetching current files in the content space and displaying them in the uploader
🚀 feat(ContentSpaceFilesUploader): add support for uploading image files to the content space using the Bytescale upload widget
🚀 feat(ContentSpaceFilesUploader): add support for displaying a dialog with the uploader when the upload button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for closing the dialog when the close button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for showing a helper text with disabled reasons
🚀 feat(ContentSpaceFilesUploader): add support for showing a loading skeleton while uploader session is not ready
🚀 feat(ContentSpaceFilesUploader): add support for fetching current files in the content space and displaying them in the uploader
🚀 feat(ContentSpaceFilesUploader): add support for uploading image files to the content space using the Bytescale upload widget
🚀 feat(ContentSpaceFilesUploader): add support for displaying a dialog with the uploader when the upload button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for closing the dialog when the close button is clicked
🚀 feat(ContentSpaceFilesUploader): add support for showing a helper text with disabled reasons
🚀 feat(ContentSpaceFilesUploader): add support for showing a loading skeleton while uploader session is not ready
🚀 feat(ContentSpaceFilesUploader): add support for fetching current files in the content space and displaying them in the uploader

🔀 refactor(ContentSpaceFilesTable): update translation keys for better consistency and clarity
🔀 refactor(ContentSpaceFilesTableClient): update translation keys for better consistency and clarity
🔀 refactor(ContentSpaceFilesUploader): update translation keys for better consistency and clarity
🔀 refactor(ContentSpaceFilesUploaderClient): update translation keys for better consistency and clarity
…ontent component to fix runtime error

🔧 fix(NextIntlServer.mock.js): add missing getMessages function to fix runtime error
…evalidate tag name

🔧 chore(ContentSpaceFiles.tsx): remove unused import and commented out code
🔧 chore(tsconfig.lib.json): fix path to types folder
🔧 chore(.babelrc): remove unused file
✨ feat(.swcrc): add new configuration file for swc
✨ feat(package.json): add new package.json file for @features/back-office/events
✨ feat(project.json): add new build executor for @nx/js:swc
🔧 chore(tsconfig.lib.json): fix path to types folder
🔧 chore(en.json): add new translation for "files"
🔧 chore(fr.json): add new translation for "files"
@sebpalluel sebpalluel merged commit 9264ed0 into staging Feb 5, 2024
10 of 12 checks passed
@sebpalluel sebpalluel deleted the 241-dca-5-create-the-content-upload-and-editing-interface branch February 5, 2024 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DCA-5: Create the Content Upload and Editing Interface
1 participant