PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Loading old enough build stops the ability to allocate nodes
Open
Nobody has claimed this yet.
bug
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
What is the expected behaviour/value?
Loading old builds should keep the tree intact
What is the actual behaviour/value?
Loading an old build from 3.8 results in an empty tree and doesn't let me allocate new nodes
How to reproduce the issue
No response
Build code
See attached build, as exporting the build saves the empty tree. Rename the file from `.zip` to `.xml`
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Load the attached STUNNYBUNNY.zip, renamed to .xml, in the current Path of Building app and compare the tree with the expected behavior. Trace handling of this 3.8 build and verify that the tree remains populated and new nodes can be allocated; add a regression check if the repository has coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100