-
Notifications
You must be signed in to change notification settings - Fork 97
chore: Merge for release #736
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Alexandre Rousseau <alexandre@rsseau.fr>
Co-authored-by: Alexandre Rousseau <alexandre@rsseau.fr>
Co-authored-by: Alexandre Rousseau <alexandre@rsseau.fr>
Co-authored-by: Alexandre Rousseau <alexandre@rsseau.fr>
Introduce a simple abstraction to use logger in the application. For the moment, it's just a proxy to `console`, but it can be plugged to any library later. It's also a good way to prevent that logs are not displayed in the tests.
The `BaseCollapseButton` used a custom button with a different `:focus` state. I moved it to the standard `WdsButton` and implemented a `:focus-visible` to it to improve tab navigation. The change should be almost transparent in term of UI.
The `BuilderSelect` trigger has overflow issues with long text containing breakable content. The trick was just a missing `white-space: nowrap` rule. I also took the opportunity to add a tooltip to the `BuilderSelect`'s trigger.
We want the user to be able to customize any style using `import_stylesheet` feature. But, actually, he needs to use `!important` everywhere to makes his rules have more weight. The solution is to use CSS cascade layers to redefine the priority of rules easily. We can move all Writer Framework CSS into a layer `wf`. This makes other CSS rules have more priority by default. So I just installed PostCSS and a plugin `postcss-assign-layer`. This automates surrounding our styles by layers.
fix(ui): floating insertion marker overflow - WF-158
fix(ui): hide `CoreProgressBar` progression in indeterminate state
* update playwright to support ubuntu 24.04
…-handle-ubuntu-2404 fix: update playwright to support ubuntu 24.04 agent for e2e test
* feat: update dependencies
* adapt version of numpy using python version * feat: update dependencies
Use `BaseMarkdown` in `CoreAnnotatedText` to support inline markdown syntax. I also reworked a bit `BaseMarkdown` to have an inline mode.
This reverts commit 8b86174.
feat(ui): support markdown in `AnnotatedText` - WF-169
stringify content in API responses as per docs; convert Framework-specific `integer` and `float` types to JSON schema-compliant `number`
feat: support python 3.13
feat(ui): introduce fields validation - WF-140
feat: implement multi-file code editor - WF-100
Hotfix: tool calls
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.