-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fixed project urls for PyPI #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nfx
added a commit
that referenced
this pull request
Apr 17, 2024
* Fixed ToC for `mocking` checker ([#29](#29)). In this release, we have made significant improvements to the `mocking` checker in our open-source library, which is specifically designed for identifying common mistakes and issues in Spark code written in Python. We have added two new rules, `R8918: explicit-dependency-required` and `R8919: obscure-mock`, which respectively check for the requirement of explicit dependencies and the use of obscure mocks. This update enhances the accuracy and quality of the code review process for Spark code written in Python, ensuring that the code meets the highest standards of quality and reliability. Additionally, we have fixed an issue in the Table of Contents (ToC) for the `mocking` checker, making it easier for users to navigate and utilize this feature. * Fixed project urls for PyPI ([#32](#32)). In this release, the `pyproject.toml` configuration file for the Python project has been updated to fix project URLs for PyPI. Specifically, the URLs for the `Issues` and `Source` fields have been changed from "<https://github.com/databrickslabs/pylint/issues>" and "<https://github.com/databrickslabs/pylint>" to "<https://github.com/databrickslabs/pylint-plugin/issues>" and "<https://github.com/databrickslabs/pylint-plugin>", respectively. This modification ensures that users can correctly report issues and access the source code for the pylint-plugin project on GitHub. The rest of the file remains unchanged. This enhancement provides a seamless experience for users who want to contribute to the project or seek support for any issues they encounter. * Updated README.md to fix pip install command ([#30](#30)). In this release, we have updated the installation command for the project to fix the pip install process. Previously, users installed the project using the command "pip install pylint-plugin-for-databricks", but this has been changed to "pip install databricks-labs-pylint". This update is part of issue [#30](#30) and is intended to improve the installation experience for users. It is important to note that no new methods have been added and no existing functionality has been changed; only the installation command has been updated. Software engineers adopting this project should use the new command to install it.
Merged
nfx
added a commit
that referenced
this pull request
Apr 17, 2024
* Fixed ToC for `mocking` checker ([#29](#29)). In this release, we have made significant improvements to the `mocking` checker in our open-source library, which is specifically designed for identifying common mistakes and issues in Spark code written in Python. We have added two new rules, `R8918: explicit-dependency-required` and `R8919: obscure-mock`, which respectively check for the requirement of explicit dependencies and the use of obscure mocks. This update enhances the accuracy and quality of the code review process for Spark code written in Python, ensuring that the code meets the highest standards of quality and reliability. Additionally, we have fixed an issue in the Table of Contents (ToC) for the `mocking` checker, making it easier for users to navigate and utilize this feature. * Fixed project urls for PyPI ([#32](#32)). In this release, the `pyproject.toml` configuration file for the Python project has been updated to fix project URLs for PyPI. Specifically, the URLs for the `Issues` and `Source` fields have been changed from "<https://github.com/databrickslabs/pylint/issues>" and "<https://github.com/databrickslabs/pylint>" to "<https://github.com/databrickslabs/pylint-plugin/issues>" and "<https://github.com/databrickslabs/pylint-plugin>", respectively. This modification ensures that users can correctly report issues and access the source code for the pylint-plugin project on GitHub. The rest of the file remains unchanged. This enhancement provides a seamless experience for users who want to contribute to the project or seek support for any issues they encounter. * Updated README.md to fix pip install command ([#30](#30)). In this release, we have updated the installation command for the project to fix the pip install process. Previously, users installed the project using the command "pip install pylint-plugin-for-databricks", but this has been changed to "pip install databricks-labs-pylint". This update is part of issue [#30](#30) and is intended to improve the installation experience for users. It is important to note that no new methods have been added and no existing functionality has been changed; only the installation command has been updated. Software engineers adopting this project should use the new command to install it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.