Skip to content

[AI Gen] Fixed typescript errors and enabled linter for cvat-core#10489

Open
bsekachev wants to merge 8 commits intodevelopfrom
bs/core_ts_check
Open

[AI Gen] Fixed typescript errors and enabled linter for cvat-core#10489
bsekachev wants to merge 8 commits intodevelopfrom
bs/core_ts_check

Conversation

@bsekachev
Copy link
Copy Markdown
Member

@bsekachev bsekachev commented Apr 16, 2026

Motivation and context

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

@bsekachev bsekachev changed the title Fixed typescript errors and enabled linter for cvat-core [AI Gen] Fixed typescript errors and enabled linter for cvat-core Apr 16, 2026
@bsekachev
Copy link
Copy Markdown
Member Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ccbfb2e408

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +1982 to +1984
private syncAggregateState(): void {
this.occluded = this.elements.every((element) => element.occluded);
this.lock = this.elements.every((element) => element.lock);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Keep skeleton lock derived after history operations

SkeletonShape now caches aggregate state in this.lock/this.occluded, but the undo/redo callbacks created in updateElements only mutate child element fields and never resync that cache. After undoing or redoing a skeleton lock change, this.elements[*].lock can differ from cached this.lock, and methods that rely on this.lock (like delete() and the early return in save()) can incorrectly treat an unlocked skeleton as locked (or vice versa).

Useful? React with 👍 / 👎.

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.

1 participant