Fixes minor Framer Motion errors

[anubrag]

This pull request addresses several minor errors discovered while using Framer Motion within the Nextpy application. The specific changes implemented include:

1. Module Renaming:

   • Old: nextpy/frontend/components/animation/framer/__init__.py
   • New: nextpy/frontend/components/animation/motion/__init__.py
   • This change reflects the adoption of Framer Motion specifically, instead of the broader term "framer".

2. Typo and Formatting Fixes:

   • Minor typos and formatting inconsistencies were corrected.

3. Test Modifications:

   • The tests/components/animation/test_framer-motion.py file was updated to reflect the new module name and functionality.

[coderabbitai]

Walkthrough

The nextpy library underwent a significant reorganization, involving updates to module path mappings and the public interface of the animation package. New modules were added, and the animation components were expanded with additional attributes and classes, while some existing elements were removed or modified. These changes suggest a broad enhancement of the library's structure and functionality.

Changes

File Path	Change Summary
nextpy/__init__.py	Reorganized module path mappings; added and removed exported entities.
.../components/animation/__init__.py	Added dynamic __all__ declaration.
.../components/animation/motion/motion.py	Added attributes and methods to FramerMotion; introduced new motion classes; removed MotionBase.
tests/.../animation/test_framer-motion.py	Modified import path; commented out test cases.

🐇✨
In the burrows of the code, a change did sweep,
Paths were woven anew, the structure deep.
With a hop and a skip, the rabbit declares,
"To the future of nextpy, nothing compares!"
🎉🚀

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 X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment from CodeRabbit.
• You can also chat with CodeRabbit bot directly around the specific lines of code or files in the PR by tagging @coderabbitai in a new comment.
• You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 8

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b6d025c and 7d866df.

Files ignored due to filter (1)

• nextpy.log

Files selected for processing (4)

• nextpy/init.py (3 hunks)
• nextpy/frontend/components/animation/init.py (1 hunks)
• nextpy/frontend/components/animation/motion/motion.py (3 hunks)
• tests/components/animation/test_framer-motion.py (4 hunks)

Additional comments: 6

nextpy/__init__.py (2)

• 251-254:
  The addition of the nextpy.backend.admin module with its attributes in the _MAPPING dictionary is consistent with the PR's objective to update module path mappings.

• 338-338:
  Raising an AttributeError with a custom message in the __getattr__ function is a good practice for debugging and understanding import errors.

tests/components/animation/test_framer-motion.py (4)

• 3-9: The import statement has been correctly updated to reflect the new module name.

• 24-27: The tests for MotionBase have been commented out. Verify that the functionality previously tested by these cases is either obsolete or covered by new tests.

• 39-45: The test case for MotionInput's animate property has been commented out. Verify that this is intentional and that the properties are tested elsewhere if still relevant.

• 36-48: > Note: This review was outside the patches, so it was mapped to the patch with the greatest overlap. Original lines [29-100]

The instantiation tests for the various motion components appear to be correct and consistent with the renaming and reorganization of the motion components.