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

Updated import module #6817

Merged
merged 2 commits into from
Jan 24, 2025
Merged

Updated import module #6817

merged 2 commits into from
Jan 24, 2025

Conversation

eshanrnh
Copy link
Contributor

Description

Fixes Issue #6797
Also, while testing the article, I had to bump the backoffice version. I added that info in the Vite Package Setup article.

Type of suggestion

  • Typo/grammar fix
  • Updated outdated content
  • New content
  • Updates related to a new version
  • Other

Product & version (if relevant)

CMS v15

Deadline (if relevant)

When should the content be published?

{% hint style="info" %}
Optionally you can use `--legacy-peer-deps` in the installation command to avoid installing Umbraco´s sub-dependencies like TinyMCE and Monaco Editor:\
`npm install --legacy-peer-deps -D @umbraco-cms/backoffice`
* Ensure that you install the version relevant to your Umbraco installation. You can find the appropriate version on the [@umbraco-cms/backoffice npm page](https://www.npmjs.com/package/@umbraco-cms/backoffice). Alternatively, you can manually update the version in your `package.json` file to match your setup.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think generally we should try to add warnings/notes related to checking specific versions, before the steps to install.
Otherwise, people might install the wrong thing, only to read this note afterwards 😅

Also, the bullets are quite long and contain a lot of info. Consider if it makes sense to just add the info to a paragraph.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense. I've tried to incorporate your review comments. Also, I made some slight changes to other steps to ensure proper flow.

Copy link
Contributor

@sofietoft sofietoft left a comment

Choose a reason for hiding this comment

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

LGTM 💪

@eshanrnh eshanrnh merged commit 578d5e9 into main Jan 24, 2025
18 of 27 checks passed
@eshanrnh eshanrnh deleted the property-editor-update branch January 24, 2025 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants