thecyberronin / ase-parser Goto Github PK

Title says it all.

Abstract parsing away from the library to allow the same lib to be used in Node vs the browser. Since the Aseprite specific code can essentially be the same, I don't see a reason why the library would have to be duplicated to support both platforms.

Add GitHub Actions for auto assigning issues and PRs as well as adding to GitHub Projects.

Update the README to include the values that may be present with the most recent PR that implemented Slice chunk

When try to set layer's visible/hidden at aseprite, I observed that the "flags" attribute of Layer Object by ase-parser from 3 to 2. What mean the "flags" value ? Is there a reasonable way to know the layer's visible ? Please ..

Handle ICC profile data correctly instead of skipping it.

Use the magic numbers in the Aseprite file to make sure that we're reading an Aseprite file and the correct chunks where implemented.

The contributing guide should include:

• Branch naming conventions
• Code Style (ESLint preferences)
• PR Guidelines
• Commenting Guidelines
• Git Flow Explanation

Need to add support for the new additions in 1.3 of Aseprite