krausandre / content-blocks-gui Goto Github PK

There is no readme yet.

• information about contribution
• information about the project

I added my custom sitepackage and this was not shown inside the dropdown for selecting the host extension.
Reason could be

The extension is not added, when it has no require-dependency for content blocks in its composer.json.

This should not happen, as we can not be sure if everybody has this dependency set. For example, if you have a composer.json for the whole project, and the dependency is set there, but not in the sitepackage.

I get this error, while having CSP for the backend active:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-WV0EnOPNpeCxINrtDdJ_VX-MpaRqEuE9v55KxxWvRYIlvUf3_hgzYg' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-1e5RR2OpHhuX2h0Bat19DsNTmqbo4M3T1pqfeTXCHaA='), or a nonce ('nonce-...') is required to enable inline execution.

t @ VM88914:1
s @ VM88914:1
c @ VM88914:1
(anonymous) @ VM88914:1

Maybe after a save, so the user couldnt click somewhere else, while it is saving.

The Notifications and Modals from TYPO3 can't be used within the vitests and later inside the website which runs outside TYPO3.

We should consider to change the TYPO3 Notifications with some kind of JS or Vue Notifications

Translate the labels inside the Vue App.

Shall we maintain the translations inside Crowdin so other people can translate the labels and download them into their TYPO3 installation?

During ddev start I get the following Error:
src/views/EditCB/PickerView.vue:31:19 - error TS2339: Property 'cloneFieldType' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<{} & VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly<...>, never>; ... 10 more ...; $watch<T extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => any : (...ar...'.

and

Property 'availableFieldTypes' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<{} & VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly<...>, never>; ... 10 more ...; $watch<T extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (args_0: R, args_1: R) => any : (...ar...'.

Veelidate or something else to validate all the input fields, checkboxes, select boxes, etc.

It is fine to access the store data directly:
https://pinia.vuejs.org/core-concepts/getters.html

Just mutations need to make sure that object changes are noticed by pinia.

Since our used version of vuedraggable is not maintained anymore (last commit october 2022) we should switch to its successor https://github.com/Alfred-Skyblue/vue-draggable-plus

_save_content_type expects

'contentBlock' => [
     'vendor' => $getParsedBody['contentBlock']['vendor'],
     'name' => $getParsedBody['contentBlock']['name'],
]

_get_cb only sets name (as "xxx/yyy" compound)

JE: I would prefer just name in _save_content_type, too.

We need to get bool/int/string/array in PHP to correctly save it as .yaml.

The HTTP transfer is encoded as multipart/form-data (because PHP does not understand JSON natively).

Currently that leads to only string/array.

Idea:
We could send a JSON string via multipart/form-data and json_decode() the whole thing once in PHP.

Maybe the table view for the overview could be inside one big table with some kind of filtering and sorting

• make the table searchable
• show all elements in only one table (discuss this first)
• try to make all columns one size

• createContentBlockContentElementConfiguration in EXT:content-blocks/Classes/Service/CreateContentType.php

• Code Quality Checks
• Test renedering of documentation

The json schema is now stored in https://github.com/nhovratov/content-blocks-json-schema

• remove the already included json schema
• include external schema

Storybook could be interesting for developing the different components.

It could be also helpfull for visual testing

Get translations of a CB: partly done

• Get default translations
• Get translation of a target language

Save translation of a CB: partly done

• save initial existing items
• save initial existing items to new target language
• save new added items (when new fields added)

Since plugins will be available, we should include them too.

At the moment this is still WIP in nhovratov/content-blocks#95

• For Content Elements
• For PageTypes
• For RecordTypes
• For Basics