Version
v1.21.1717686938 (pre-release)
Areas for Improvement

[ ] UI/UX
[ ] Onboarding
[ ] Docs
[X] Chat
[ ] Commands
[ ] Context
[ ] Response Quality
[ ] Other

What needs to be improved? Please describe how this affects the user experience and include a screenshot.

there no more stop button
Describe the solution you'd like to see
bring back the stop button, sometimes u wont wait for the full answer. time is money :)
Describe any alternatives that could be considered
No response
Additional context
No response
### Tasks

Yes, we will bring this back. In the meantime, you can press Esc (hidden keyboard shortcut).
However: It is not possible to reply until the message has completed yet. We could make this possible, but we're not sure of the impact of a partial chopped-off message on the reply response quality. You can edit your message while it's still streaming in. We also turned off autoscroll by default, so you should be able to just ignore the message continuing to stream in. Not disputing that a button is useful and expected, but I'm curious about why you actually want it or if it just feels bad for the message to keep streaming in.

I think the idea is to stop the message (ESC button does the trick), not edit, and trigger a new message. Not sure if possible, why not make those options configurable?


Upgraded to Ember 2.x

Hi @jimmay5469 @elwayman02, I was just going to start on a side project which needs Github issues and I didn't want to write adapters from scratch. I saw that you folks were trying to get this up to speed on 2.x libs. So I've ported them. It has passing tests and I'm planning to raise PRs to introduce issues and labels but the upgrade is my first step towards that. Let me know if there's anything more required in this PR. Cheers 😄
Implements #9

Fixes #10

@sivakumar-kailasam this looks awesome! This repo has been third or so on my list to deal with, but I hadn't gotten to it yet. I really appreciate all the work you've done here, it looks great. I left a few minor comments on the PR, but once we address those I think this is good to go. Thanks!

@elwayman02 I was feeling twitchy 😉 about updating the version no too. I've addressed the feedback from the comments in the latest commit. Looking forward to raising further PRs so that I can finally start using it on my project 😄

I just headed to bed, but I'll look at this again in the morning and get it
merged if we're good! Thanks again. :)
On Sun, Apr 10, 2016, 2:49 AM Sivakumar Kailasam<EMAIL_ADDRESS>wrote:

@elwayman02 https://github.com/elwayman02 I was feeling twitchy 😉
about updating the version no too. I've addressed the feedback from the
comments in the latest commit. Looking forward to raising further PRs so
that I can finally start using it on my project 😄
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/elwayman02/ember-data-github/pull/10#issuecomment-207951403

Sure, wfm! Good night :)


feat: add form slot for action area

Description

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
[ ] Run the tests with pnpm test.
[ ] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

New Features

Introduced new customizable slots in the Form Actions component for enhanced flexibility: reset-before, submit-before, advance-before, and advance-after.

Improvements

Enhanced code organization and readability by streamlining import statements and template structures across components.

lint没通过

已重新提交


feat(get-schema): added JSON and console output options

Added JSON output (works with watch too)
Added console output
Refactored get-schema for better type safety

Related to #16.
Closes #13.

@kbrandwijk great PR! would you mind rebasing and resolving the conflicts?

@schickling Done!


Force claim error string not in language file, probably hard coded

Description:
Force claim string is not in language file, probably hard coded
This should be in the language file
You are scanning a different RuuviTag
Related iOS card: https://github.com/ruuvi/com.ruuvi.station.ios/issues/2083

Search for "claim_wrong_sensor_scanned" in localization

Moving to done, Android is good


[BUG] Scraper workflow error

Describe the bug

Please see @krokkie

Fixed.   Limpopo's figures moved a bit on the pictures....