Closed taefi closed 2 months ago
Why is package-lock.json
changed without any corresponding change to package.json
?
Why is
package-lock.json
changed without any corresponding change topackage.json
?
Good catch. That was unintentionally committed/pushed. Reverted.
Attention: Patch coverage is 92.85714%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 92.58%. Comparing base (
03d9b0f
) to head (fd70ae0
).
Files | Patch % | Lines |
---|---|---|
packages/ts/react-crud/src/autogrid-columns.tsx | 0.00% | 0 Missing and 1 partial :warning: |
packages/ts/react-signals/src/Signals.ts | 87.50% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
7 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
This ticket/PR has been released with Hilla 24.5.0.alpha6 and is also targeting the upcoming stable 24.5.0 version.
Description
Add basic support for full-stack
NumberSignal
type to be returned by endpoints as a shared signal instance that supports number value operations. The client-side user code (for now) need to do manual wrapping of the needed metadata about the endpoint method(s) that return shared signal instance(s).Assuming a simple endpoint returning a
NumberSignal
instance like this:The needed manually written user code is like this (this will be generated later):
Then then usage of this wrapping service in views could be similar to what is described in the related issue:
NOTE: Since the Full-stack signals are experimental for now, please don't forget to enable the
fullstackSignals
feature flag in your applications (by adding the following insrc/main/resources/vaadin-featureflags.properties
):Fixes #2429
Type of change
Checklist
Additional for
Feature
type of change