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

feat(sandbox): add checkbox for translatable property #361

Merged
merged 8 commits into from
Mar 7, 2024

Conversation

BibiSebi
Copy link
Contributor

@BibiSebi BibiSebi commented Feb 20, 2024

What?

Added new checkbox 'Translatable' to easily develop by being able to turn on and off the functionality. This PR includes the following changes:

  • Adding a new checkbox to manipulate the translatable property
  • Renaming the Options title of a section to Settings
  • Reflecting changes of translatable and storyLang inside the code block
Screenshot 2024-02-20 at 16 52 31

Why?

JIRA: EXT-2240

Copy link

vercel bot commented Feb 20, 2024

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

Name Status Preview Comments Updated (UTC)
plugin-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 7, 2024 10:45am

})
const [content, setContent] = useState<unknown>(initialContent)
const [language, setLanguage] = useState<string>('')
const [language, setLanguage] = useState<string>('default')
Copy link
Contributor Author

Choose a reason for hiding this comment

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

inside storyfront I noticed that the default language seems to be set to 'default'

const [stateChangedCallbackId, setStateChangedCallbackId] = useState<string>()

const stateChangedData = useMemo<StateChangedMessage>(
() => ({
model: content,
schema: schema,
interfaceLanguage: 'en',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was added due to type issues of StateChangedMessage which forced me to add this line of code.

@BibiSebi BibiSebi requested a review from eunjae-lee February 20, 2024 15:57
@BibiSebi BibiSebi force-pushed the EXT-2240-update-sandbox branch from d500c26 to 104d6b6 Compare February 20, 2024 16:44
@BibiSebi BibiSebi marked this pull request as ready for review February 21, 2024 08:45
@BibiSebi
Copy link
Contributor Author

I just realized that this PR should not have been stacked. We will need to release a new version of field-plugin library and then redeploy the sandbox.

Copy link
Contributor

@eunjae-lee eunjae-lee left a comment

Choose a reason for hiding this comment

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

Looks good to me! If you want to merge this later, then I think you could merge #360 first, and run gt restack on this branch to rebase on the updated main branch. What do you think?

@BibiSebi BibiSebi force-pushed the EXT-2240-update-sandbox branch from 104d6b6 to 8b83b41 Compare February 22, 2024 09:44
Base automatically changed from EXT-2238-update-field-plugin to main February 22, 2024 10:45
@demetriusfeijoo demetriusfeijoo force-pushed the EXT-2240-update-sandbox branch from 8d28e4c to 8b83b41 Compare March 1, 2024 21:57
@eunjae-lee
Copy link
Contributor

@BibiSebi anything else you need me to review about this PR? :)

@BibiSebi
Copy link
Contributor Author

BibiSebi commented Mar 4, 2024

@eunjae-lee no, this is just blocked by the field plugin release which is blocked by the storyfront release :D

@BibiSebi BibiSebi merged commit 5444303 into main Mar 7, 2024
4 checks passed
@BibiSebi BibiSebi deleted the EXT-2240-update-sandbox branch March 7, 2024 10:56
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