We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Aligning text on an index view is no longer working and the default spacing and alignment for badges has changed.
Steps to reproduce the behavior:
html: {index: {wrapper: {classes: "text-right"}}})
Expected behaviour is for the field contents to be right aligned instead it being left aligned.
Avo version: 3.15.6 / 3.15.7
Rails version: 8.0.0
Ruby version: 3.3.6
License type:
Are you using Avo monkey patches, overriding views or view components?
With Avo 3.15.5 the right and centre alignment is working. The column 'MONTANT' is right aligned and the 'COMMENTAIRES' is center aligned.
But not with 3.15.6 and 3.15.7:
The cause is possibly the addition of an extra div in feature: copyable field option.
div
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Aligning text on an index view is no longer working and the default spacing and alignment for badges has changed.
Reproduction repository for the bug
Steps to use in the reproduction repository
Steps to reproduce the behavior:
html: {index: {wrapper: {classes: "text-right"}}})
Expected behavior & Actual behavior
Expected behaviour is for the field contents to be right aligned instead it being left aligned.
System configuration
Avo version: 3.15.6 / 3.15.7
Rails version: 8.0.0
Ruby version: 3.3.6
License type:
Are you using Avo monkey patches, overriding views or view components?
Screenshots or screen recordings
With Avo 3.15.5 the right and centre alignment is working. The column 'MONTANT' is right aligned and the 'COMMENTAIRES' is center aligned.
But not with 3.15.6 and 3.15.7:
Additional context
The cause is possibly the addition of an extra
div
in feature: copyable field option.Impact
Urgency
The text was updated successfully, but these errors were encountered: