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

added basename to be visible on create language use case #48

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

sabinabarbu
Copy link

No description provided.

@royteeuwen
Copy link
Contributor

royteeuwen commented Nov 14, 2024

@sabinabarbu thanks for the PR. I do think that this alone will not show the basename though. Can you show a screenshot where you show the result of the change? By default the basename is already shown when creating a new dictionary? See screenshot:
Screenshot 2024-11-14 at 20 35 03
Screenshot 2024-11-14 at 20 35 23

@bdhoine bdhoine self-requested a review November 14, 2024 19:55
@bdhoine
Copy link
Collaborator

bdhoine commented Nov 14, 2024

@sabinabarbu and when adding a language you get the basename from the overview page, what do you want to achieve?

Copy link
Collaborator

@bdhoine bdhoine left a comment

Choose a reason for hiding this comment

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

see also questions in conversation ;)

@@ -0,0 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
Copy link
Collaborator

Choose a reason for hiding this comment

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

this will add a field but it's nowhere included in a dialog

Copy link
Author

@sabinabarbu sabinabarbu Nov 15, 2024

Choose a reason for hiding this comment

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

@sabinabarbu
Copy link
Author

sabinabarbu commented Nov 15, 2024

The fix is for create language use case not for create dictionary. In this file below you can find basename field used but it was not defined.
"basename
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/include"
path="/apps/aem-dictionary-translator/content/granite/field/basename"

After the fix, basename is visible when creating the language:
image

@bdhoine
Copy link
Collaborator

bdhoine commented Nov 15, 2024

@sabinabarbu thanks for your contribution, while checking the specs (https://sling.apache.org/documentation/bundles/internationalization-support-i18n.html#resourcebundle-with-base-names-1) we see that a basename actually can be multivalued, would you mind contributing that as well?

Please also update the CHANGELOG.md

@royteeuwen
Copy link
Contributor

any idea on when / if you could provide the update @sabinabarbu ? We'd want to cut a release when the pr's of @kwin are merged :)

@sabinabarbu
Copy link
Author

any idea on when / if you could provide the update @sabinabarbu ? We'd want to cut a release when the pr's of @kwin are merged :)

I don't know exactly when I get the time for this.

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