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

docs: announce version 17 #2065

Merged
merged 13 commits into from
Apr 15, 2024
Merged

Conversation

profanis
Copy link
Contributor

WIP

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

@nx-cloud
Copy link

nx-cloud bot commented Sep 26, 2023

☁️ Nx Cloud Report

CI is running/has finished running commands for commit de99dad. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 3 targets

Sent with 💌 from NxCloud.

@bundlemon
Copy link

bundlemon bot commented Sep 26, 2023

BundleMon (Integration Projects)

Unchanged files (2)
Status Path Size Limits
Main bundles(Gzip)
hello-world-ng17/dist-integration/main.(hash)
.js
68.5KB +1%
Main bundles(Gzip)
hello-world-ng16/dist-integration/main.(hash)
.js
67.03KB +1%

No change in files bundle size

Final result: ✅

View report in BundleMon website ➡️


Current branch size history | Target branch size history

@profanis profanis force-pushed the docs/announce_3.9 branch 3 times, most recently from 0c86e73 to de99dad Compare October 30, 2023 15:02
Copy link

nx-cloud bot commented Mar 11, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 370ea7f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 4 targets

Sent with 💌 from NxCloud.

@profanis profanis force-pushed the docs/announce_3.9 branch from d0ff7dd to 0cebaa9 Compare April 10, 2024 07:51
@profanis profanis changed the title docs: announce 3.9 docs: announce version 17 Apr 10, 2024
@profanis profanis marked this pull request as ready for review April 10, 2024 08:00
Copy link
Contributor

@joaqcid joaqcid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@markwhitfeld markwhitfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feedback from a quick review

@profanis profanis requested a review from markwhitfeld April 12, 2024 12:58

NGXS provides a robust error handling mechanism that automatically catches unhandled exceptions thrown within actions. These errors are then directed to a centralized `ErrorHandler`.

However, you can override the default implementation and provide your custom one
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, you can override the default implementation and provide your custom one
However, you can override the default implementation and provide your custom one.


---

## Plugin Improvements
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that plugin improvements should be placed at the end. This is because it describes that some of the symbols are now privately exported, which is less prioritized compared to other information we're providing in these docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point! I moved it just before the NGXS Community section. My thought was to have the NGXS community section as the closure.
Do you think the Plugin Improvements should be the last section of the readme?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should have the discord link at the very top, like 'first of all, we're moving to discord' or something?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two things about the Discord question

  1. Is this "move" to Discord in relation to Slack being the default currently (from what I can tell at the moment)? I joined the Slack recently as it seemed to be pinned to the top of the README.md. If so, in my opinion I definitely would highlight the move to Discord towards the top of this announcement post, or at the least not at the very bottom.
  2. If I am correct in this assumption, make sure to update the README.md badge as well as I assume the NGXS Labs contact part.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your comment @michael-small
Indeed makes sense to move that on top. As of your second point, the README.md file has been updated and currently is part of the development version

@profanis profanis requested a review from arturovt April 13, 2024 12:14
Copy link

@michael-small michael-small left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two questions about this version, reading this as if I had no context with what is going on now. Technically I don't know as much anyways, but I know I have had the pleasure of meeting up with some team members recently so I am reading this article with some more context than most other users who will read this post.

  1. The article declares that this is NGXS 17, but the branch name is announcing 3.9. Are versions from NGXS 17+ going to be 1:1 with Angular majors? If so, in my opinion I would highlight this in the article.
  2. I don't know what the compatibility matrix of Angular versions to NGXS would be with NGXS 17, but if it is different than previous version upgrades I would also call this out in the announcement. At least the minimum version to use the standalone and signal changes.

Copy link
Member

@markwhitfeld markwhitfeld left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the changes!
@michael-small makes very good points. Could you add a paragraph at the beginning about aligning versions with Angular, in order to readily take advantage of the latest features as the framework continues to evolve.
And a mention of the minimum version required for the signals and standalone support.

@profanis profanis requested a review from markwhitfeld April 15, 2024 10:30
Copy link

codeclimate bot commented Apr 15, 2024

Code Climate has analyzed commit 370ea7f and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 95.3% (0.0% change).

View more on Code Climate.

@markwhitfeld markwhitfeld merged commit fc98e14 into ngxs:master Apr 15, 2024
12 checks passed
@markwhitfeld markwhitfeld added this to the v.18.0.0 milestone Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants