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

[Documentation]Adding notes for latest linux version and libwebkit issue #3806

Merged
merged 4 commits into from
Oct 20, 2024

Conversation

pratikmota
Copy link
Contributor

@pratikmota pratikmota commented Oct 7, 2024

Description

  • For latest linux os(ex: Ubuntu 24.04) libwebkit 4.0 is not supported so wails doctor will give error. We need to install 4.1 version and use tags while building.
  • In current Installation documentation these information was not added, I come to know from discord group discussion.
  • Given documentation changes will be helpful for community who are using linux.
    image
  • Issue with 4.0 version
sudo apt install libwebkit2gtk-4.0-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package libwebkit2gtk-4.0-dev
E: Couldn't find any package by glob 'libwebkit2gtk-4.0-dev'
  • resolution
  1. sudo apt install libwebkit2gtk-4.1-dev
  2. wails build -tags webkit2_41

Please delete options that are not relevant.

  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration using wails doctor.

  • Windows
  • macOS
  • Linux

Test Configuration

Please paste the output of wails doctor. If you are unable to run this command, please describe your environment in as much detail as possible.

  • As it is only documentation update, wails doctor not needed to test.
  • Adding screenshot for localhost testing
    image

Checklist:

  • I have updated website/src/pages/changelog.mdx with details of this PR
  • My code follows the general coding style of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Summary by CodeRabbit

  • Bug Fixes

    • Resolved multiple issues including memory problems, JSON errors, and build issues on macOS and Windows.
    • Fixed drag-and-drop functionality and dialog issues on Windows.
  • Documentation

    • Updated changelog to reflect version v2.9.2 changes.
    • Enhanced installation documentation for Linux, addressing potential issues with libwebkit dependencies and providing solutions for newer distributions.

Copy link
Contributor

coderabbitai bot commented Oct 7, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request include updates to the changelog and installation documentation for version v2.9.2 of the project, released on September 18, 2024. The changelog now details fixes and changes made in this version, including various bug fixes and documentation updates. Additionally, the installation documentation for version v2.9.0 has been revised to address platform-specific dependencies for Linux, providing guidance on handling issues with the libwebkit package.

Changes

File Change Summary
website/src/pages/changelog.mdx Updated changelog for version v2.9.2, detailing fixes and changes, including multiple bug fixes.
website/versioned_docs/version-v2.9.0/gettingstarted/installation.mdx Added note on Linux dependencies, addressing libwebkit issues and providing installation guidance.
website/docs/gettingstarted/installation.mdx Similar update as above, added note on Linux dependencies for libwebkit and installation guidance.

Possibly related PRs

Poem

In the garden where changes bloom,
Bugs fixed, like flowers, dispel the gloom.
With notes for Linux, clear and bright,
Our project grows, a wondrous sight!
Hops of joy, we celebrate,
Version v2.9.2, oh, what a fate! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pratikmota pratikmota marked this pull request as ready for review October 7, 2024 03:43
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
website/versioned_docs/version-v2.9.0/gettingstarted/installation.mdx (1)

61-62: Approved with a suggestion for improvement

The added note provides valuable information for users encountering issues with libwebkit on the latest Linux versions. It addresses the problem described in the PR objectives and offers a clear solution.

To further improve clarity, consider adding a specific example of the command to use during the build process. This will help users understand exactly how to apply the suggested tag.

Here's a suggested addition to the note:

 If you are using latest Linux version (example: Ubuntu 24.04) and it is not supporting <code>libwebkit2gtk-4.0-dev</code>, then you might encounter an issue in <code>wails doctor</code>: <code>libwebkit</code> not found. To resolve this issue you can install <code>libwebkit2gtk-4.1-dev</code> and during your build use the tag <code>-tags webkit2_41</code>.
+For example, you can use the following command to build your application:
+<code>wails build -tags webkit2_41</code>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a6288c4 and 1fcf247.

📒 Files selected for processing (2)
  • website/src/pages/changelog.mdx (1 hunks)
  • website/versioned_docs/version-v2.9.0/gettingstarted/installation.mdx (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
website/versioned_docs/version-v2.9.0/gettingstarted/installation.mdx (1)

61-62: Overall assessment: Valuable addition to the documentation

The changes made to the Linux section of the installation guide effectively address the issue with libwebkit on the latest Linux versions, as described in the PR objectives. This addition provides important information for users who might encounter this problem, offering a clear solution and improving the overall user experience.

The content is well-integrated into the existing document structure and maintains consistency with the style of the rest of the guide. With the minor suggestion for improvement implemented, this change will significantly enhance the documentation for Linux users.

@leaanthony leaanthony enabled auto-merge (squash) October 10, 2024 09:16
@leaanthony
Copy link
Member

@pratikmota - Can you please add the changes to the non-versioned documentation please. Thanks 🙏

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
website/docs/gettingstarted/installation.mdx (1)

61-62: Approve the addition of libwebkit installation note for latest Linux versions.

The added note provides valuable information for users of the latest Linux distributions, specifically addressing the issue with libwebkit2gtk-4.0-dev and offering a solution. This addition aligns well with the PR objectives and the AI-generated summary.

Some suggestions for improvement:

  1. Consider adding a specific command for installing the package:
    sudo apt install libwebkit2gtk-4.1-dev
    
  2. Provide the full build command with the tag:
    wails build -tags webkit2_41
    
  3. For clarity, you might want to separate the installation and build instructions into two sentences.

Here's a suggested revision for improved clarity:

<br/><strong>Note:</strong><br/>
If you are using the latest Linux version (e.g., Ubuntu 24.04) and encounter an issue with `wails doctor` reporting "`libwebkit` not found", it may be because `libwebkit2gtk-4.0-dev` is not supported. To resolve this, install `libwebkit2gtk-4.1-dev` using the command: `sudo apt install libwebkit2gtk-4.1-dev`. When building your project, use the tag `-tags webkit2_41` like this: `wails build -tags webkit2_41`.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 1fcf247 and b45f06a.

📒 Files selected for processing (1)
  • website/docs/gettingstarted/installation.mdx (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
website/docs/gettingstarted/installation.mdx (1)

Line range hint 1-62: Consider updating non-versioned documentation

While the changes made are valuable and address the issue with libwebkit on latest Linux versions, it's important to note that these updates are currently only reflected in the versioned documentation (v2.9.0).

As per the PR comments, there's a request to add these changes to the non-versioned documentation as well. This ensures that all users, regardless of the version they're using, have access to this important information.

To ensure consistency across documentation, please run the following script to check for non-versioned installation documentation:

If non-versioned documentation is found, please update it with the same information about libwebkit installation for the latest Linux versions.

✅ Verification successful

Non-versioned documentation is up to date

The non-versioned installation documentation (website/docs/gettingstarted/installation.mdx) already includes the necessary updates regarding the libwebkit installation for the latest Linux versions. No further action is required.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for non-versioned installation documentation

# Search for non-versioned installation.mdx files
echo "Searching for non-versioned installation.mdx files:"
fd --type f "installation.mdx" website/docs | grep -v "/v[0-9]"

# If found, display their content
fd --type f "installation.mdx" website/docs | grep -v "/v[0-9]" | xargs -I {} sh -c 'echo "\nContent of {}:"; cat {}'

Length of output: 4336

@pratikmota
Copy link
Contributor Author

@pratikmota - Can you please add the changes to the non-versioned documentation please. Thanks 🙏

@leaanthony : I have updated changes in website/docs/gettingstarted/installation.mdx
My understanding:

  • Previously updated changes in below file:
    wails/website/versioned_docs/version-v2.9.0/gettingstarted/installation.mdx

  • As per your comment I need to update same changes to below file.

    wails/website/docs/gettingstarted/installation.mdx
    Please correct me if i am missing something or not understood properly.
    Doubt:
    Inside i18n languages folder text changes will apply automatically by GitHub Actions. I will not require to change anything right?

@leaanthony leaanthony merged commit 5ebccf1 into wailsapp:master Oct 20, 2024
4 of 6 checks passed
@leaanthony
Copy link
Member

Thank you! 🙏

Copy link

sonarcloud bot commented Oct 20, 2024

@pratikmota
Copy link
Contributor Author

@leaanthony : Thank you very much for merge. This was my first contribution in Wails. :-) I will keep contributing this project.

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.

2 participants