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

Put each seatalk-datagram into an own file #1

Closed
3 tasks done
arnegue opened this issue Mar 17, 2024 · 1 comment
Closed
3 tasks done

Put each seatalk-datagram into an own file #1

arnegue opened this issue Mar 17, 2024 · 1 comment

Comments

@arnegue
Copy link
Owner

arnegue commented Mar 17, 2024

The file seatalk_datagram.py has currently 1533 lines and contains 89 classes. Time to refactor and bring them into an own file each.

  • Put each datagram into own file
  • Create a directory "datagram" in seatalk and put every file there
  • remove redundant "datagram"-suffix
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
arnegue added a commit that referenced this issue Mar 17, 2024
@arnegue
Copy link
Owner Author

arnegue commented Mar 17, 2024

Merged with: #5

@arnegue arnegue closed this as completed Mar 17, 2024
arnegue added a commit that referenced this issue Apr 18, 2024
arnegue added a commit that referenced this issue Apr 19, 2024
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

No branches or pull requests

1 participant