ayo/lion
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: update urls to use new one (#2619)

Browse source 
* chore(docs): update URLs to lion.js.org
* chore(docs): use correct url for versioning rationale
This commit is contained in:
Ayo Ayco 2025-11-14 14:59:08 +01:00 committed by GitHub
parent b64f520680
commit c0d5e1918e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 10 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -26,15 +26,15 @@
</p>
<p align="center">
<a href="https://lion-web.netlify.app">Website</a>
<a href="https://lion.js.org">Website</a>
·
<a href="https://lion-web.netlify.app/fundamentals/">Fundamentals</a>
<a href="https://lion.js.org/fundamentals/">Fundamentals</a>
·
<a href="https://lion-web.netlify.app/guides/">Guides</a>
<a href="https://lion.js.org/guides/">Guides</a>
·
<a href="https://lion-web.netlify.app/components/">Components</a>
<a href="https://lion.js.org/components/">Components</a>
·
<a href="https://lion-web.netlify.app/blog/">Blog</a>
<a href="https://lion.js.org/blog/">Blog</a>
</p>
**Lion is a set of highly performant, accessible and flexible Web Components.!**
@ -51,7 +51,7 @@ They provide an unopinionated, white-label layer that can be extended to your ow
> This makes sense as the main use case is to extend those components and if you do you do not want to override existing stylings.
<p align="center">
<a href="https://lion-web.netlify.app/guides/"><strong>Explore the Lion Guides&nbsp;&nbsp;▶</strong></a>
<a href="https://lion.js.org/guides/"><strong>Explore the Lion Guides&nbsp;&nbsp;▶</strong></a>
</p>
## Astro migration
@ -182,7 +182,7 @@ This means you only have to apply your own Design System: by delivering styles,
## Coding guidelines
Check out our [coding guidelines](https://lion-web.netlify.app/guides/principles/definitions-and-terms/) for more detailed information.
Check out our [coding guidelines](https://lion.js.org/guides/principles/definitions-and-terms/) for more detailed information.
## How to contribute

2
packages-node/providence-analytics/CHANGELOG.md
View file

@ -219,7 +219,7 @@
**We also unfixed lion's dependencies (now using caret ^) on its own packages**, because it caused a lot of problems with duplicate installations for end users as well as subclassers and its end users. Both of these changes may affect subclassers in a breaking manner, hence the minor bump.
Be sure to [read our Rationale on this change](https://lion-web.netlify.app/docs/rationales/versioning/) and what this means for you as a user.
Be sure to [read our Rationale on this change](https://lion.js.org/fundamentals/rationales/versioning/) and what this means for you as a user.
## 0.12.4

9
packages/ajax/CHANGELOG.md
View file

@ -147,7 +147,6 @@
With the upgrade to `@open-wc/scoped-elements` v2.1.1 Lion now no longer automatically loads the polyfill through `ScopedElementsMixin`.
This essentially means the polyfill became optional which results in the following behavior
1. If polyfill is not loaded it will use the global registry as a fallback
2. Log error if actually scoping is needed and polyfill is not loaded
3. If you manually create elements you will need to handle polyfilled and not polyfilled cases now
@ -179,8 +178,7 @@
or you want to use the same tag name with different implementations (use tag color-picker from foo here and from bar here)
See more details at
- [Lion release blog post](https://lion-web.netlify.app/blog/lion-without-polyfills/)
- [Lion release blog post](https://lion.js.org/blog/lion-without-polyfills/)
- [@open-wc/scoped-elements release blog post](https://open-wc.org/blog/scoped-elements-without-polyfill/)
- [Change log of ScopedElementsMixin](https://github.com/open-wc/open-wc/blob/master/packages/scoped-elements/CHANGELOG.md#210)
@ -192,7 +190,7 @@
**We also unfixed lion's dependencies (now using caret ^) on its own packages**, because it caused a lot of problems with duplicate installations for end users as well as subclassers and its end users. Both of these changes may affect subclassers in a breaking manner, hence the minor bump.
Be sure to [read our Rationale on this change](https://lion-web.netlify.app/docs/rationales/versioning/) and what this means for you as a user.
Be sure to [read our Rationale on this change](https://lion.js.org/fundamentals/rationales/versioning/) and what this means for you as a user.
## 0.12.1
@ -205,7 +203,6 @@
### Minor Changes
- 87959850: **BREAKING** public API changes:
- Changed `timeToLive` to `maxAge`
- Renamed `requestIdentificationFn` to `requestIdFunction`
@ -224,7 +221,6 @@
### Minor Changes
- 73d4e222: **BREAKING** public API changes:
- `AjaxClient` is now `Ajax`
- `AjaxClientFetchError` is now `AjaxFetchError`
- `request` and `requestJson` methods of `Ajax` class are renamed as `fetch` and `fetchJson` respectively
@ -244,7 +240,6 @@
### Minor Changes
- 43e4bb81: Type fixes and enhancements:
- all protected/private entries added to form-core type definitions, and their dependents were fixed
- a lot @ts-expect-error and @ts-ignore (all `get slots()` and `get modelValue()` issues are fixed)
- categorized @ts-expect-error / @ts-ignore into: