Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solid v1.7 #1638

Merged
merged 43 commits into from
Mar 30, 2023
Merged

Solid v1.7 #1638

merged 43 commits into from
Mar 30, 2023

Conversation

ryansolid
Copy link
Member

@ryansolid ryansolid commented Mar 21, 2023

This PR shows the upcoming changes for Solid 1.7. You can try it out on thenext branch of git and beta tag on npm. It has numbering like v1.7.0-beta.3.

This release has a lot of TypeScript breaking changes. We've been pretty lenient on TS breaking changes in minors so we are keeping that trend, but I'm particularly concerned with this one. So I'd appreciate the ecosystem to try it out and give some feedback leading up to the release. On the positive all the TS fixes will be backwards compatible. We've just gotten more strict with the JSX mostly, so bending to that won't break any older versions of Solid.

I will publish beta versions of related packages (like vite-plugin-solid) so that you can try this. Most packages should just work with their latest versions.

thetarnav and others added 29 commits February 14, 2023 11:22
* Organize exports, export not exported types from signal.ts

Exported types: `AccessorArray`, `EffectFunction`, `MemoOptions`, `NoInfer`, `OnEffectFunction`

* Format and minor cleanup

abstract `ComputationState` type, inline `get` of defined property

* Rework dev hooks, add `debugValue` utility

* Correct the type of `DevComponent` interface

assuming the return value of `JSX.Element` is wrong,
as this only applies if the component get's rendered

* Correct type of `SignalState`

* Add graph owner to sourceMap values

* Reorder store imports

* Reorder imports

* Remove `afterWriteSignal` hook

* add changeset

---------

Co-authored-by: Ryan Carniato <[email protected]>
* Remove name generation of owners and signals

* Rename SignalMapValue to SourceMapValue

* add changeset

---------

Co-authored-by: Ryan Carniato <[email protected]>
* Fix castError

* Strongly type onError

---------

Co-authored-by: Ryan Carniato <[email protected]>
* Add component funciton to dev component

* Create nice-dogs-draw.md
@changeset-bot
Copy link

changeset-bot bot commented Mar 21, 2023

🦋 Changeset detected

Latest commit: af34922

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
solid-js Patch
test-integration Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coveralls
Copy link

coveralls commented Mar 21, 2023

Pull Request Test Coverage Report for Build 4529509779

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 209 of 219 (95.43%) changed or added relevant lines in 10 files are covered.
  • 38 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.7%) to 93.485%

Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/solid/src/reactive/signal.ts 83 85 97.65%
packages/solid/src/render/flow.ts 67 75 89.33%
Files with Coverage Reduction New Missed Lines %
packages/solid/web/src/index.ts 2 93.96%
packages/solid/src/reactive/signal.ts 36 93.62%
Totals Coverage Status
Change from base Build 4528367340: -0.7%
Covered Lines: 4063
Relevant Lines: 4286

💛 - Coveralls

@juanrgm
Copy link
Contributor

juanrgm commented Mar 21, 2023

41 errors in SUID due to #1554.

@lxsmnsyc
Copy link
Member

@juanrgm this is expected. solid-headless is also going to be affected by this

@ryansolid
Copy link
Member Author

Yeah to clarify I'm expecting a bunch of errors as this is stricter. It is more trying to determine if there is any truly awkward pieces. I don't think the errors effect external facing APIs.. just internals of libraries or applications themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants