pi-spaces 0.0.0-stage β 0.16.1
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/CHANGELOG.md +368 -0
- package/LICENSE +21 -0
- package/README.md +627 -2
- package/dist/command.js +210 -0
- package/dist/config.js +414 -0
- package/dist/context.js +66 -0
- package/dist/herdr.js +224 -0
- package/dist/launch.js +86 -0
- package/dist/relaunch.js +251 -0
- package/dist/spaces.js +384 -0
- package/extensions/spaces.ts +106 -0
- package/package.json +74 -4
- package/skills/pi-spaces/SKILL.md +59 -0
- package/src/command.ts +210 -0
- package/src/config.ts +414 -0
- package/src/context.ts +66 -0
- package/src/herdr.ts +224 -0
- package/src/launch.ts +86 -0
- package/src/relaunch.ts +251 -0
- package/src/spaces.ts +384 -0
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,368 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
Each release of `pi-spaces` (published as `@jals1212/pi-spaces` up to 0.15.1). Versions follow
|
|
4
|
+
[semantic versioning](https://semver.org); before 1.0.0 a minor version may add
|
|
5
|
+
commands and options and a patch version fixes.
|
|
6
|
+
|
|
7
|
+
## Unreleased
|
|
8
|
+
|
|
9
|
+
## 0.16.1
|
|
10
|
+
|
|
11
|
+
### Changed
|
|
12
|
+
|
|
13
|
+
- The `pi-spaces` skill and the README say that `pi-space setup` runs in base too,
|
|
14
|
+
for a profile that has a setup command (pi-spaces-cli 0.17.0); the built-in `pi`
|
|
15
|
+
has none.
|
|
16
|
+
|
|
17
|
+
## 0.16.0
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
|
|
21
|
+
- The package is now published as `pi-spaces`, without the `@jals1212` scope;
|
|
22
|
+
`@jals1212/pi-spaces` stops at 0.15.1 and is deprecated. To move, replace
|
|
23
|
+
`npm:@jals1212/pi-spaces` with `npm:pi-spaces` in the `packages` of every
|
|
24
|
+
`settings.json` that declares it (the base home and each space), or run
|
|
25
|
+
`pi remove npm:@jals1212/pi-spaces` and `pi install npm:pi-spaces`. Keep only
|
|
26
|
+
one of the two: both together load `/space` twice. The library exports are
|
|
27
|
+
now `pi-spaces/spaces` and `pi-spaces/config`.
|
|
28
|
+
|
|
29
|
+
## 0.15.1
|
|
30
|
+
|
|
31
|
+
### Fixed
|
|
32
|
+
|
|
33
|
+
- herdr-app sidebar: an agent no longer loses its space after the Herdr app is
|
|
34
|
+
closed and opened. The `space` label was set once, and a set that failed while
|
|
35
|
+
herdr-core was starting (or a core restarted under a running Pi) left the
|
|
36
|
+
terminal without it. The session now follows `hc events` for its terminal and
|
|
37
|
+
sets the label again when it is missing or changed, following the stream again
|
|
38
|
+
with backoff when it ends. A label removed while the session lasts, by
|
|
39
|
+
anything, comes back the same way.
|
|
40
|
+
|
|
41
|
+
## 0.15.0
|
|
42
|
+
|
|
43
|
+
### Documentation
|
|
44
|
+
|
|
45
|
+
- The README explains that the extension and the `pi-space` command are independent: use either one, or both, with what each one gives and cannot do alone.
|
|
46
|
+
|
|
47
|
+
## 0.14.0
|
|
48
|
+
|
|
49
|
+
### Added
|
|
50
|
+
|
|
51
|
+
- Herdr sidebar: the status line text (`πͺ <profile>/<name>`) also shows in Herdr's
|
|
52
|
+
Agents sidebar. In a Herdr pane it is the pane's `$space` metadata token
|
|
53
|
+
(30-second TTL, refreshed every 10 seconds, cleared when the session ends),
|
|
54
|
+
shown by a `$space` row item; in a herdr-app terminal it is the terminal's
|
|
55
|
+
`space` label (`hc label`), set once, removed when the session ends or moves
|
|
56
|
+
to another terminal. Display only. The README shows how to add both to the
|
|
57
|
+
sidebar.
|
|
58
|
+
|
|
59
|
+
## 0.13.0
|
|
60
|
+
|
|
61
|
+
### Added
|
|
62
|
+
|
|
63
|
+
- The config file can be TOML: a path ending in `.toml` is read as TOML (with
|
|
64
|
+
`#` comments), any other as JSON as before. Both have the same keys and
|
|
65
|
+
checks. TOML is parsed with the `smol-toml` dependency.
|
|
66
|
+
- `configFile(env, home)` returns the config file and, when there is one, the
|
|
67
|
+
`config.json` that a `config.toml` in the same folder shadows.
|
|
68
|
+
|
|
69
|
+
### Changed
|
|
70
|
+
|
|
71
|
+
- The config file is looked up as `config.toml`, then `config.json`, in
|
|
72
|
+
`~/.config/pi-spaces` (or `$XDG_CONFIG_HOME/pi-spaces`), then in
|
|
73
|
+
`~/.pi-spaces`; with no file the answer of `configPath` is
|
|
74
|
+
`~/.pi-spaces/config.toml` (it was `~/.pi-spaces/config.json`). An existing
|
|
75
|
+
`config.json` keeps working where it is.
|
|
76
|
+
- When `config.toml` and `config.json` are in the same folder, `config.toml` is
|
|
77
|
+
read and the extension warns that the `config.json` is ignored.
|
|
78
|
+
|
|
79
|
+
## 0.12.0
|
|
80
|
+
|
|
81
|
+
### Added
|
|
82
|
+
|
|
83
|
+
- A space is a root folder with its agent home inside it, always named `agent`:
|
|
84
|
+
`<spaces folder>/<name>/agent` is `PI_CODING_AGENT_DIR` (and `{home}`) for every
|
|
85
|
+
profile, as `~/.pi/agent` is for Pi's own home. `/space new` and
|
|
86
|
+
`createSpace` make the root with `agent/settings.json`. Spaces made before,
|
|
87
|
+
with no `agent/` folder, keep working as they are (their folder is the agent
|
|
88
|
+
home); list, rename, remove, backups, `/space switch` and the active-space
|
|
89
|
+
detection work for both layouts, and rename, remove and backups act on the
|
|
90
|
+
root.
|
|
91
|
+
- `{space}` in `spaceEnv` values and in `commands` and `setup`: the space's root
|
|
92
|
+
folder (the same folder as `{home}` for an old space; in base, the folder that
|
|
93
|
+
holds the profile's `home`). `expandSpaceEnv`, `spaceEnvFor` and `setupCommand`
|
|
94
|
+
take it as an optional last argument.
|
|
95
|
+
- `spaceHome(root)`, `isRooted(root)`, `AGENT` and `migrateSpace(...)` in
|
|
96
|
+
`@jals1212/pi-spaces/spaces`: `migrateSpace` copies an old space to
|
|
97
|
+
`.backups/<name>-<UTC time>`, then moves its content into `<root>/agent`,
|
|
98
|
+
undoing the moves if one fails. See
|
|
99
|
+
[Moving an old space](README.md#moving-an-old-space).
|
|
100
|
+
|
|
101
|
+
### Changed
|
|
102
|
+
|
|
103
|
+
- `createSpace` returns the space's root (as before) but writes
|
|
104
|
+
`settings.json` in `<root>/agent`. `SwitchTarget` and `LaunchTarget` carry
|
|
105
|
+
`spaceRoot`, and `targetHome` of a space with an `agent/` folder is that
|
|
106
|
+
folder. `PI_SPACE_HOME` is the space's agent home.
|
|
107
|
+
|
|
108
|
+
## 0.11.3
|
|
109
|
+
|
|
110
|
+
### Added
|
|
111
|
+
|
|
112
|
+
- A preview image (`pi.image`) for the Pi package gallery, also shown at the
|
|
113
|
+
top of the README.
|
|
114
|
+
|
|
115
|
+
## 0.11.2
|
|
116
|
+
|
|
117
|
+
### Fixed
|
|
118
|
+
|
|
119
|
+
- `/space switch` with a v2 profile runs the profile's `commands` (`commands.base`
|
|
120
|
+
for base, `commands.space` or `<base> --space <name>` for a space) instead of
|
|
121
|
+
starting the running Pi again, so a launcher's own setup for base is kept. A
|
|
122
|
+
Pi started with `--space` no longer returns to that space after a switch.
|
|
123
|
+
|
|
124
|
+
## 0.11.1
|
|
125
|
+
|
|
126
|
+
### Changed
|
|
127
|
+
|
|
128
|
+
- The docs and the skill use a generic launcher in their examples; the README
|
|
129
|
+
keeps one example profile for a real program.
|
|
130
|
+
|
|
131
|
+
## 0.11.0
|
|
132
|
+
|
|
133
|
+
### Added
|
|
134
|
+
|
|
135
|
+
- Config schema `pi-spaces.config/v2`: a profile has `commands` instead of
|
|
136
|
+
`command`, `setup` and `homeless`. `commands.base` starts the base home as it
|
|
137
|
+
is (the words after it, no `--space`); `commands.space` is the template of a
|
|
138
|
+
space, with `{home}` and `{name}` (without it a space starts
|
|
139
|
+
`<base> --space <name>`); `commands.setup` prepares a new space. For a v2
|
|
140
|
+
profile `PI_SPACES_COMMAND` is `commands.space`, else `commands.base`, and
|
|
141
|
+
`PI_SPACES_SETUP` is `commands.setup`. A v1 file keeps working unchanged;
|
|
142
|
+
[Moving from v1 to v2](README.md#moving-from-v1-to-v2) shows the edit. An
|
|
143
|
+
older pi-spaces refuses a v2 file as "needs a newer pi-spaces", so update
|
|
144
|
+
every home before switching the file.
|
|
145
|
+
- The config file accepts `//` and `/* */` comments, in both schemas.
|
|
146
|
+
|
|
147
|
+
### Changed
|
|
148
|
+
|
|
149
|
+
- The `SCHEMA` export of `@jals1212/pi-spaces/config` is now
|
|
150
|
+
`pi-spaces.config/v2`; `SCHEMA_V1` is the first schema. The "needs a newer
|
|
151
|
+
pi-spaces" message names both: `this one reads "pi-spaces.config/v1" and
|
|
152
|
+
"pi-spaces.config/v2"`, and a v2 profile's unknown-key message lists
|
|
153
|
+
`"home", "commands", "dir" and "spaceEnv"`.
|
|
154
|
+
- The `<pi_space>` prompt section says `pi-space <profile>/<name>` starts a
|
|
155
|
+
space when the command has `{name}` as well as `{home}`.
|
|
156
|
+
|
|
157
|
+
## 0.10.0
|
|
158
|
+
|
|
159
|
+
### Added
|
|
160
|
+
|
|
161
|
+
- A profile may list `homeless` words (`"homeless": ["upgrade"]`): with one of
|
|
162
|
+
them first, `pi-space` runs the profile's `command` without its home part
|
|
163
|
+
and without `--space`, so `pi-space gentle/base upgrade` runs
|
|
164
|
+
`gentle-shell upgrade`. A non-empty list of words with no spaces; anything
|
|
165
|
+
else is refused like any wrong key. An older pi-spaces refuses a file with
|
|
166
|
+
`homeless` as an unknown key, so update every home before adding it.
|
|
167
|
+
|
|
168
|
+
### Fixed
|
|
169
|
+
|
|
170
|
+
- The README and the skill no longer say that `pi-space gentle/base upgrade`
|
|
171
|
+
runs gentle-shell's `upgrade` through `--home`: gentle-shell recognizes it
|
|
172
|
+
only as its first word, so after `--home` it goes to Pi. `homeless` covers it.
|
|
173
|
+
|
|
174
|
+
## 0.9.0
|
|
175
|
+
|
|
176
|
+
### Added
|
|
177
|
+
|
|
178
|
+
- A profile `command` may contain `{home}` and `{name}`
|
|
179
|
+
(`"gentle-shell --home {home}"`): `pi-space` then runs it directly in the
|
|
180
|
+
space's home, without `--space`, so the program's own commands work
|
|
181
|
+
(`pi-space gentle/base upgrade`). The `<pi_space>` section of the system
|
|
182
|
+
prompt then says that `pi-space <profile>/<name>` starts a space, not
|
|
183
|
+
`<command> --space <name>`.
|
|
184
|
+
- The config file is also found in `~/.config/pi-spaces/config.json`
|
|
185
|
+
(`$XDG_CONFIG_HOME/pi-spaces/config.json` when `XDG_CONFIG_HOME` is an
|
|
186
|
+
absolute path; on Windows `%USERPROFILE%\.config\pi-spaces\config.json`),
|
|
187
|
+
so it can live in your dotfiles without `PI_SPACES_CONFIG`. Order:
|
|
188
|
+
`PI_SPACES_CONFIG`, then that file when it exists, then
|
|
189
|
+
`~/.pi-spaces/config.json` as before; with both files the XDG one wins, and
|
|
190
|
+
nothing is moved. `configPath(env, home)` takes an optional existence check.
|
|
191
|
+
|
|
192
|
+
## 0.8.0
|
|
193
|
+
|
|
194
|
+
### Changed
|
|
195
|
+
|
|
196
|
+
- πͺ is pi-spaces' emoji. The status line shows the active space as
|
|
197
|
+
`πͺ <profile>/<name>` instead of `β <name>`, the same name `pi-space`
|
|
198
|
+
takes, with the profile of the running Pi (`pi` when no profile matches its
|
|
199
|
+
base home); in the base home opened by pi-spaces it shows
|
|
200
|
+
`πͺ <profile>/base` instead of `β base`.
|
|
201
|
+
|
|
202
|
+
## 0.7.0
|
|
203
|
+
|
|
204
|
+
### Changed
|
|
205
|
+
|
|
206
|
+
- The setup hint of `/space new` names the space with its profile, as
|
|
207
|
+
`pi-space` now requires: `pi-space setup <profile>/<name>`, where the
|
|
208
|
+
profile is the one of the running Pi (`pi` when no profile matches its base
|
|
209
|
+
home). `/space` itself still takes the bare name.
|
|
210
|
+
|
|
211
|
+
### Fixed
|
|
212
|
+
|
|
213
|
+
- The built-in `pi` profile no longer takes another profile's home: inside
|
|
214
|
+
the Pi of a program whose profile names its `home`, `PI_CODING_AGENT_DIR`
|
|
215
|
+
holds that home, and `pi` now keeps `~/.pi/agent` (its spaces in
|
|
216
|
+
`~/.pi/spaces`) instead of pointing at that program's home and spaces.
|
|
217
|
+
|
|
218
|
+
## 0.6.0
|
|
219
|
+
|
|
220
|
+
### Added
|
|
221
|
+
|
|
222
|
+
- Profiles in a config file (`~/.pi-spaces/config.json`, or `PI_SPACES_CONFIG`):
|
|
223
|
+
named descriptions of a program that runs Pi, with its base `home`,
|
|
224
|
+
`command`, spaces `dir`, `setup` command and `spaceEnv`. The format carries a
|
|
225
|
+
version (`"schema": "pi-spaces.config/v1"`); a newer version is refused with
|
|
226
|
+
a message that it needs a newer pi-spaces, and unknown keys are refused. A
|
|
227
|
+
built-in `pi` profile always exists and can be replaced. See the README.
|
|
228
|
+
- `spaceEnv`: variables that exist only in spaces. Entering a space sets them
|
|
229
|
+
(`{home}` and `{name}` filled in) and moving between spaces recomputes
|
|
230
|
+
them. Going back to `base` puts back the values the base home had (kept in `PI_SPACES_BASE_ENV` meanwhile). Without
|
|
231
|
+
`spaceEnv`, whatever a program keeps outside its agent home stays shared with
|
|
232
|
+
the base home, as before. The variables pi-spaces sets itself are refused.
|
|
233
|
+
- The extension applies the profile whose `home` is the base home: its
|
|
234
|
+
`spaceEnv` on `/space switch` and `pi --space`, its `dir` as the spaces
|
|
235
|
+
folder, and `/space new` names `pi-space setup <name>` when it has a `setup`.
|
|
236
|
+
- `@jals1212/pi-spaces/config` exports the loader (`loadConfig`, `configPath`,
|
|
237
|
+
`profileByName`, `profileForHome`, `spaceEnvFor`, `activeProfile`,
|
|
238
|
+
`ConfigError`) for the `pi-space` command.
|
|
239
|
+
|
|
240
|
+
### Changed
|
|
241
|
+
|
|
242
|
+
- `completion` is a reserved name, for `pi-space completion`. A space already
|
|
243
|
+
named `completion` is no longer listed; rename its folder by hand.
|
|
244
|
+
- The spaces folder is `PI_SPACES_DIR`, else the matching profile's `dir`, else
|
|
245
|
+
`spaces` next to the base home. `spacesDir` takes the profile's dir as an
|
|
246
|
+
optional third argument.
|
|
247
|
+
- `relaunchEnv` and `planStartup` take an optional `spaceEnv`; without it they
|
|
248
|
+
behave exactly as before.
|
|
249
|
+
- A config file that cannot be used never stops Pi: the extension warns once
|
|
250
|
+
when the session starts and behaves as with no file.
|
|
251
|
+
|
|
252
|
+
## 0.5.0
|
|
253
|
+
|
|
254
|
+
### Added
|
|
255
|
+
|
|
256
|
+
- `/space new` names `pi-space setup <name>` when `PI_SPACES_SETUP` holds a
|
|
257
|
+
setup command, so a space a program needs prepared is not entered bare.
|
|
258
|
+
|
|
259
|
+
### Changed
|
|
260
|
+
|
|
261
|
+
- `setup` is a reserved name, as the other command words are. A space already
|
|
262
|
+
named `setup` is no longer listed; rename its folder by hand.
|
|
263
|
+
|
|
264
|
+
## 0.4.1
|
|
265
|
+
|
|
266
|
+
### Changed
|
|
267
|
+
|
|
268
|
+
- The status line shows `β base` in the base home when pi-spaces opened it
|
|
269
|
+
(`pi --space base`, `pi-space base`, or a switch back to base); Pi started
|
|
270
|
+
plainly still shows nothing there.
|
|
271
|
+
|
|
272
|
+
## 0.4.0
|
|
273
|
+
|
|
274
|
+
### Added
|
|
275
|
+
|
|
276
|
+
- `pi --space <name> <command> [args...]` runs one of Pi's package commands
|
|
277
|
+
(`install`, `remove`, `uninstall`, `update`, `list`) in a space, or in the
|
|
278
|
+
base home with `base`, through the same Pi: `pi --space work update
|
|
279
|
+
--extensions`. Options before `--space`, such as a launcher's own `-e`, are
|
|
280
|
+
left out, since Pi runs a package command only as its first argument.
|
|
281
|
+
|
|
282
|
+
### Changed
|
|
283
|
+
|
|
284
|
+
- The command words `list`, `new`, `remove`, `rename`, `switch`, `update`,
|
|
285
|
+
`install` and `uninstall` are reserved and can no longer name a space, so
|
|
286
|
+
`pi-space <name>` never reads as a command. A folder with such a name in the
|
|
287
|
+
spaces folder is no longer listed as a space.
|
|
288
|
+
|
|
289
|
+
## 0.3.0
|
|
290
|
+
|
|
291
|
+
### Added
|
|
292
|
+
|
|
293
|
+
- Pi knows the space it runs in. Every Pi with the extension sets
|
|
294
|
+
`PI_SPACE` (unset in the base home), `PI_SPACE_HOME` (its agent home) and
|
|
295
|
+
`PI_SPACES_COMMAND` (its configured value, else `pi`), with or without a
|
|
296
|
+
switch, and the system prompt gets a `<pi_space>` section with the same
|
|
297
|
+
facts. `spaceInfo`, `exportSpaceInfo` and `spacePrompt` in the core build
|
|
298
|
+
them.
|
|
299
|
+
- A `pi-spaces` skill, declared in the package, that tells agents what a
|
|
300
|
+
space is, how to read the current space, home and command, and which
|
|
301
|
+
`/space` or `pi-space` action to use.
|
|
302
|
+
|
|
303
|
+
### Changed
|
|
304
|
+
|
|
305
|
+
- The status line shows the active space as `β <name>` instead of
|
|
306
|
+
`space: <name>`, so it stands out among other extensions' statuses.
|
|
307
|
+
|
|
308
|
+
## 0.2.0
|
|
309
|
+
|
|
310
|
+
### Added
|
|
311
|
+
|
|
312
|
+
- `/space remove` asks, after the confirmation, whether to keep a backup:
|
|
313
|
+
the space moves to `.backups/<name>-<UTC time>` in the spaces folder, and
|
|
314
|
+
keeping one is the first choice. `--yes` keeps a backup, and `--no-backup`
|
|
315
|
+
deletes without one. `backupSpace` and `BACKUPS` in the core do it, with the
|
|
316
|
+
same checks as `removeSpace`.
|
|
317
|
+
|
|
318
|
+
### Changed
|
|
319
|
+
|
|
320
|
+
- `/space remove <name> --yes` now keeps a backup instead of deleting the
|
|
321
|
+
space; add `--no-backup` to delete it as before.
|
|
322
|
+
|
|
323
|
+
### Fixed
|
|
324
|
+
|
|
325
|
+
- `/space new` copies a local path that loads another copy of this package
|
|
326
|
+
(a folder whose `package.json` is named `@jals1212/pi-spaces`) instead of
|
|
327
|
+
writing the folder of the copy that runs.
|
|
328
|
+
- `/space remove` and `backupSpace` report a backup that cannot be written
|
|
329
|
+
(for example a read-only spaces folder) as an error that says the space was
|
|
330
|
+
not removed and offers `--no-backup`, instead of a raw filesystem error.
|
|
331
|
+
- `findOwnDeclaration` takes an optional fallback, answered when nothing
|
|
332
|
+
matches, and an empty package folder matches a local path only by its
|
|
333
|
+
`package.json` name.
|
|
334
|
+
|
|
335
|
+
## 0.1.1
|
|
336
|
+
|
|
337
|
+
### Changed
|
|
338
|
+
|
|
339
|
+
- The `pi-space` command moved to its own package, `@jals1212/pi-spaces-cli`, so each one is installed and updated on its own; this package is now only the Pi extension.
|
|
340
|
+
|
|
341
|
+
### Fixed
|
|
342
|
+
|
|
343
|
+
- The README, the `pi-space --help` text and the examples name no particular
|
|
344
|
+
program that runs Pi; they use a generic `my-launcher`. 0.1.0 is withdrawn
|
|
345
|
+
from npm: use 0.1.1.
|
|
346
|
+
|
|
347
|
+
## 0.1.0
|
|
348
|
+
|
|
349
|
+
### Added
|
|
350
|
+
|
|
351
|
+
- Named spaces: separate Pi agent homes in a `spaces` folder next to the home
|
|
352
|
+
Pi starts with (`~/.pi/spaces` for `~/.pi/agent`), or `PI_SPACES_DIR`.
|
|
353
|
+
- `/space` opens a picker of the other spaces and restarts Pi in the chosen
|
|
354
|
+
one; without the interactive terminal it lists them. `/space list`,
|
|
355
|
+
`/space new <name>`, `/space switch [<name>]`, `/space rename <old> <new>`
|
|
356
|
+
and `/space remove <name>`. `base` is the home Pi started with. (#1, #4)
|
|
357
|
+
- The switch restarts Pi with the same options and moves every variable that
|
|
358
|
+
points into the old home, so a program that runs Pi with its own home keeps
|
|
359
|
+
working. (#1, #3)
|
|
360
|
+
- `pi --space <name>` starts Pi directly in a space, keeping the prompt and the
|
|
361
|
+
session options. (#1)
|
|
362
|
+
- The active space in the status line.
|
|
363
|
+
- The optional `pi-space` command (`npm install -g`): a numbered picker,
|
|
364
|
+
`pi-space <name> [pi args...]` and `pi-space list`. `PI_SPACES_COMMAND`
|
|
365
|
+
chooses the program it runs. (#2)
|
|
366
|
+
- `remove` and `rename` refuse `base`, the active space, symlinks, a space that
|
|
367
|
+
holds the current or base home, and a spaces folder that is the filesystem
|
|
368
|
+
root, the home folder or the agent home.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Jeffrey LeΓ³n
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|