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

feat: Get active counts of attribute #92

Merged
merged 3 commits into from
Oct 1, 2024
Merged

Conversation

Ashutosh619-sudo
Copy link
Contributor

@Ashutosh619-sudo Ashutosh619-sudo commented Sep 27, 2024

https://app.clickup.com/1864988/v/l/6-901603904304-1

Summary by CodeRabbit

  • New Features

    • Enhanced error handling with detailed feedback for parameter issues.
    • Updated data retrieval to count only active records.
  • Bug Fixes

    • Improved response handling for failed requests.
  • Chores

    • Updated package version from 1.22.5 to 1.23.0.

Copy link

coderabbitai bot commented Sep 27, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve enhancements to the error handling in the __post_request method of the api_base.py file, where a WrongParamsError is raised for failed responses. Additionally, the count method has been updated to include a filter that only counts records with an 'active' status, modifying the data retrieval logic accordingly. The setup.py file reflects a version update from 1.22.5 to 1.23.0.

Changes

File Change Summary
sageintacctsdk/apis/api_base.py - Added a line in __post_request to raise a WrongParamsError for failed responses.
- Updated the count method to filter for records with a status of 'active'.
setup.py - Version updated from 1.22.5 to 1.23.0.

Suggested reviewers

  • NileshPant1999
  • anishfyle

Poem

In the garden where data blooms,
A rabbit hops through code-filled rooms.
With errors caught and counts refined,
Active records now aligned.
Hooray for changes, bright and new,
A joyful leap, we bid adieu! 🐇✨


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.

Copy link

@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: 1

🧹 Outside diff range and nitpick comments (1)
sageintacctsdk/apis/api_base.py (1)

Line range hint 1-605: Summary of changes and recommendations

  1. The error handling improvement in the __post_request method is a positive change that enhances the SDK's ability to provide detailed feedback.

  2. The modification to the count method to only count active records is a significant change that may affect existing implementations. To address this:

    • Consider making the active status filter optional through a method parameter.
    • Update the method name and/or docstring to clearly reflect its behavior.
    • Ensure that this change is documented in the SDK's changelog and release notes.
  3. General recommendation: When making changes that alter the behavior of public methods, always consider backwards compatibility and provide clear documentation of the changes.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7633e7d and d1ef442.

📒 Files selected for processing (1)
  • sageintacctsdk/apis/api_base.py (2 hunks)
🔇 Additional comments (1)
sageintacctsdk/apis/api_base.py (1)

204-204: LGTM: Improved error handling

This addition enhances the error handling by raising a WrongParamsError with a specific exception message when the response status indicates a failure. It's consistent with the existing error handling pattern and provides more detailed feedback to the user.

Comment on lines +362 to +364
'filter': {
'equalto': {'field': 'STATUS', 'value': 'active'}
},
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Consider the impact of filtering only active records

The addition of a filter to only count active records is a significant change in the behavior of the count method. While this may be the desired functionality, it has several implications:

  1. It changes the expected behavior of the method without updating the method signature or docstring.
  2. Existing code that relies on this method to get a total count of all records (including inactive ones) may now produce incorrect results.

Consider the following improvements:

  1. Update the method name to reflect its new behavior (e.g., count_active).
  2. Add a parameter to make the active status filter optional, allowing users to choose whether they want to count all records or only active ones.
  3. Update the method's docstring to clearly explain the behavior and any parameters.

Example implementation:

def count(self, active_only: bool = True):
    """
    Count the number of records.
    
    :param active_only: If True, only count active records. If False, count all records. Default is True.
    :return: The count of records.
    """
    get_count = {
        'query': {
            'object': self.__dimension,
            'select': {
                'field': 'RECORDNO'
            },
            'pagesize': '1'
        }
    }
    
    if active_only:
        get_count['query']['filter'] = {
            'equalto': {'field': 'STATUS', 'value': 'active'}
        }

    response = self.format_and_send_request(get_count)
    return int(response['data']['@totalcount'])

This approach maintains backwards compatibility while allowing for the new functionality.

@ashwin1111
Copy link
Contributor

@Ashutosh619-sudo pls bump version as well

@Ashutosh619-sudo Ashutosh619-sudo merged commit f4cdf4c into master Oct 1, 2024
1 check passed
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