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

Make non-structural NodeType information administrable #44

Open
3 tasks
ambroisemaupate opened this issue Feb 13, 2025 · 1 comment · May be fixed by #50
Open
3 tasks

Make non-structural NodeType information administrable #44

ambroisemaupate opened this issue Feb 13, 2025 · 1 comment · May be fixed by #50
Labels
2.5 enhancement New feature or request

Comments

@ambroisemaupate
Copy link
Member

ambroisemaupate commented Feb 13, 2025

Make node-type and node-type fields some values overrideable per environment. With no synchronization!

  • Add a new NodeTypeDecorator entity linked to doctrine with a node_type_decorator table containing these columns: path, property, value.
  • Override NodeTypes and NodeTypeFields properties with decorated values
  • Add UI

Overrideable values examples:

  • NodeType displayName
  • NodeType description
  • NodeType color
  • NodeTypeField label
  • NodeTypeField universal
  • NodeTypeField description
  • NodeTypeField placeholder
  • NodeTypeField visible
  • NodeTypeField minLength and maxLength

Overrided values MUST NOT have any impact on structure and nodes behaviours. It should only be esthetic overrides.

This should only occur in Backoffice: this feature should not be executed on API calls and should not impact API performances.

@ambroisemaupate
Copy link
Member Author

Maybe create a second NodeTypes bag, which will be only used on Backoffice: DecoratedNodeTypes. This bag would be a mirror of NodeTypes but including all NodeTypeDecorator overrides.

@ambroisemaupate ambroisemaupate added enhancement New feature or request 2.5 labels Feb 18, 2025
@eliot488995568 eliot488995568 linked a pull request Feb 20, 2025 that will close this issue
@eliot488995568 eliot488995568 linked a pull request Feb 20, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.5 enhancement New feature or request
Development

Successfully merging a pull request may close this issue.

1 participant