@lunora/angular 0.0.1 → 1.0.0-alpha.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE.md ADDED
@@ -0,0 +1,111 @@
1
+ # Functional Source License, Version 1.1, Apache 2.0 Future License
2
+
3
+ ## Abbreviation
4
+
5
+ FSL-1.1-Apache-2.0
6
+
7
+ ## Notice
8
+
9
+ Copyright 2026 anolilab and contributors
10
+
11
+ ## Terms and Conditions
12
+
13
+ ### Licensor ("We")
14
+
15
+ The party offering the Software under these Terms and Conditions.
16
+
17
+ ### The Software
18
+
19
+ The "Software" is each version of the software that we make available under
20
+ these Terms and Conditions, as indicated by our inclusion of these Terms and
21
+ Conditions with the Software.
22
+
23
+ ### License Grant
24
+
25
+ Subject to your compliance with this License Grant and the Patents,
26
+ Redistribution and Trademark clauses below, we hereby grant you the right to
27
+ use, copy, modify, create derivative works, publicly perform, publicly display
28
+ and redistribute the Software for any Permitted Purpose identified below.
29
+
30
+ ### Permitted Purpose
31
+
32
+ A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
33
+ means making the Software available to others in a commercial product or service
34
+ that:
35
+
36
+ 1. substitutes for the Software;
37
+
38
+ 2. substitutes for any other product or service we offer using the Software that
39
+ exists as of the date we make the Software available; or
40
+
41
+ 3. offers the same or substantially similar functionality as the Software.
42
+
43
+ Permitted Purposes specifically include using the Software:
44
+
45
+ 1. for your internal use and access;
46
+
47
+ 2. for non-commercial education;
48
+
49
+ 3. for non-commercial research; and
50
+
51
+ 4. in connection with professional services that you provide to a licensee using
52
+ the Software in accordance with these Terms and Conditions.
53
+
54
+ ### Patents
55
+
56
+ To the extent your use for a Permitted Purpose would necessarily infringe our
57
+ patents, the license grant above includes a license under our patents. If you
58
+ make a claim against any party that the Software infringes or contributes to the
59
+ infringement of any patent, then your patent license to the Software ends
60
+ immediately.
61
+
62
+ ### Redistribution
63
+
64
+ The Terms and Conditions apply to all copies, modifications and derivatives of
65
+ the Software.
66
+
67
+ If you redistribute any copies, modifications or derivatives of the Software,
68
+ you must include a copy of or a link to these Terms and Conditions and not
69
+ remove any copyright notices provided in or with the Software.
70
+
71
+ ### Disclaimer
72
+
73
+ THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
74
+ IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
75
+ PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
76
+
77
+ IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
78
+ SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN
79
+ IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
80
+
81
+ ### Trademarks
82
+
83
+ Except for displaying the License Details and identifying us as the origin of
84
+ the Software, you have no right under these Terms and Conditions to use our
85
+ trademarks, trade names, service marks or product names.
86
+
87
+ ## Grant of Future License
88
+
89
+ We hereby irrevocably grant you an additional license to use the Software under
90
+ the Apache License, Version 2.0 that is effective on the second anniversary of
91
+ the date we make the Software available. On or after that date, you may use the
92
+ Software under the Apache License, Version 2.0, in which case the following will
93
+ apply:
94
+
95
+ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
96
+ this file except in compliance with the License.
97
+
98
+ You may obtain a copy of the License at
99
+
100
+ http://www.apache.org/licenses/LICENSE-2.0
101
+
102
+ Unless required by applicable law or agreed to in writing, software distributed
103
+ under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
104
+ CONDITIONS OF ANY KIND, either express or implied. See the License for the
105
+ specific language governing permissions and limitations under the License.
106
+
107
+ <!-- DEPENDENCIES -->
108
+ <!-- /DEPENDENCIES -->
109
+
110
+ <!-- TYPE_DEPENDENCIES -->
111
+ <!-- /TYPE_DEPENDENCIES -->
package/README.md CHANGED
@@ -1,45 +1,88 @@
1
1
  # @lunora/angular
2
2
 
3
- ## ⚠️ IMPORTANT NOTICE ⚠️
3
+ > **Experimental** this package is outside the Lunora 1.0 stability promise: its API may change in any release, without a major version bump.
4
4
 
5
- **This package is created solely for the purpose of setting up OIDC (OpenID Connect) trusted publishing with npm.**
5
+ Angular reactive adapter for Lunora signal-based live queries and mutations.
6
6
 
7
- This is **NOT** a functional package and contains **NO** code or functionality beyond the OIDC setup configuration.
7
+ Thin, idiomatic glue over the framework-neutral `@lunora/client`. Angular signals
8
+ map directly onto Lunora's per-subscription deltas, so a live query is just a
9
+ `signal` the WebSocket writes to.
8
10
 
9
- ## Purpose
11
+ ## Install
10
12
 
11
- This package exists to:
12
- 1. Configure OIDC trusted publishing for the package name `@lunora/angular`
13
- 2. Enable secure, token-less publishing from CI/CD workflows
14
- 3. Establish provenance for packages published under this name
13
+ ```bash
14
+ pnpm add @lunora/angular
15
+ ```
15
16
 
16
- ## What is OIDC Trusted Publishing?
17
+ `@angular/core` is a peer dependency (the host app supplies the Angular runtime).
17
18
 
18
- OIDC trusted publishing allows package maintainers to publish packages directly from their CI/CD workflows without needing to manage npm access tokens. Instead, it uses OpenID Connect to establish trust between the CI/CD provider (like GitHub Actions) and npm.
19
+ ## Wire the client
19
20
 
20
- ## Setup Instructions
21
+ Add `provideLunora` to your application config. It defaults to the page origin
22
+ (the single-worker deploy where `/_lunora/ws` loops back into the app's own
23
+ worker); pass options to point at a remote URL.
21
24
 
22
- To properly configure OIDC trusted publishing for this package:
25
+ ```ts
26
+ import { provideLunora } from "@lunora/angular";
23
27
 
24
- 1. Go to [npmjs.com](https://www.npmjs.com/) and navigate to your package settings
25
- 2. Configure the trusted publisher (e.g., GitHub Actions)
26
- 3. Specify the repository and workflow that should be allowed to publish
27
- 4. Use the configured workflow to publish your actual package
28
+ export const appConfig: ApplicationConfig = {
29
+ providers: [provideLunora(/* { url: "https://api.example.com" } */)],
30
+ };
31
+ ```
28
32
 
29
- ## DO NOT USE THIS PACKAGE
33
+ ## Live queries
30
34
 
31
- This package is a placeholder for OIDC configuration only. It:
32
- - Contains no executable code
33
- - Provides no functionality
34
- - Should not be installed as a dependency
35
- - Exists only for administrative purposes
35
+ `liveQuery` opens a subscription and mirrors every server delta into a `signal`.
36
+ It tears the subscription down automatically when the component is destroyed
37
+ (`DestroyRef.onDestroy`). Call it from an injection context — a component/service
38
+ field initializer or constructor.
36
39
 
37
- ## More Information
40
+ ```ts
41
+ import { Component } from "@angular/core";
42
+ import { liveQuery } from "@lunora/angular";
38
43
 
39
- For more details about npm's trusted publishing feature, see:
40
- - [npm Trusted Publishing Documentation](https://docs.npmjs.com/generating-provenance-statements)
41
- - [GitHub Actions OIDC Documentation](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)
44
+ import { api } from "../lunora/_generated/api";
42
45
 
43
- ---
46
+ @Component({
47
+ selector: "app-messages",
48
+ standalone: true,
49
+ template: `@for (m of messages()?.messages ?? []; track m.id) {
50
+ <p>{{ m.text }}</p>
51
+ }`,
52
+ })
53
+ export class MessagesComponent {
54
+ readonly messages = liveQuery(api.messages.list, { channelId: "general" });
55
+ }
56
+ ```
44
57
 
45
- **Maintained for OIDC setup purposes only**
58
+ Pass `"skip"` as the args to short-circuit (no network call, no socket).
59
+
60
+ ## Mutations
61
+
62
+ ```ts
63
+ import { injectLunoraClient, mutate } from "@lunora/angular";
64
+
65
+ @Component({/* … */})
66
+ export class Composer {
67
+ private readonly client = injectLunoraClient();
68
+
69
+ send(text: string) {
70
+ // Capture the client in a field: mutations fire from event handlers,
71
+ // which run outside an injection context.
72
+ return mutate(api.messages.send, { text }, { client: this.client });
73
+ }
74
+ }
75
+ ```
76
+
77
+ Optimistic updates (`optimistic` / `optimisticUpdate`) and the offline queue pass
78
+ straight through to `client.mutation`.
79
+
80
+ ## Connection status
81
+
82
+ ```ts
83
+ import { connectionStatus } from "@lunora/angular";
84
+
85
+ readonly status = connectionStatus(); // Signal<"idle" | "connecting" | "connected" | "offline">
86
+ ```
87
+
88
+ Part of the [Lunora](https://github.com/anolilab/lunora) framework.