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

INT-2756: add statusbar attribute #56

Merged
merged 5 commits into from
Jan 8, 2024
Merged

INT-2756: add statusbar attribute #56

merged 5 commits into from
Jan 8, 2024

Conversation

lorenzo-pomili
Copy link
Collaborator

@lorenzo-pomili lorenzo-pomili commented Dec 19, 2023

INT-2756
issue: #24

@lorenzo-pomili lorenzo-pomili requested a review from a team as a code owner December 19, 2023 08:03
@lorenzo-pomili lorenzo-pomili requested review from spocke, TheSpyder, ltrouton, a team, lostkeys, hamza0867 and vpyshnenko and removed request for a team December 19, 2023 08:03
Copy link
Member

@spocke spocke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need a changelog item?

@lorenzo-pomili
Copy link
Collaborator Author

@spocke changelog entry added, have a look

CHANGELOG.md Outdated Show resolved Hide resolved
@@ -48,6 +48,7 @@ const parseNumberOrString = (value: string) => /^\d+$/.test(value) ? Number.pars

const configAttributes: Record<string, (v: string) => unknown> = {
setup: parseGlobal, // function
statusbar: parseBooleanOrString, // boolean
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be // boolean or string

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought the same, but it is a boolean: https://www.tiny.cloud/docs/tinymce/latest/statusbar-configuration-options/#statusbar

I think we both confused with toolbar

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, then parseBooleanOrString should be parseBoolean ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used that because is what is used for other fields like powerpaste_allow_local_images and images_upload_credentials, maybe I'm wrong but the attribute will be always a string so even true and false will be "true" and "false"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right since they are all strings it needs to check for specific values or fallback to the string value. Makes sense now. I really should have spent time to look thought the webcomponent plugin this sprint but all other stuff came in between.

@lorenzo-pomili lorenzo-pomili merged commit 3dd9741 into main Jan 8, 2024
4 checks passed
@lorenzo-pomili lorenzo-pomili deleted the feature/INT-2756 branch January 8, 2024 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants