get_file_diff doesn't work for projects that changed schema

Open
#196 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by tracing get_file_diff and get_versions_with_file_changes, focusing on how file_history entries are handled when a schema change leaves no diff. Reproduce a version range containing a schema change, then verify that the unsupported range produces the intended exception rather than attempting a file diff.

Written by the indexing model from the issue text.

Description

bug

If you change the schema there is no diff in file_history, but this version is still in get_versions_with_file_changes returned list.

Probably for such case the function should return exception that diff is not supported for this version range.

Dominant language
Python
Stars
23
Forks
12
Avg merge
2d 13h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/python-api-client

All issues in MerginMaps/python-api-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.