Hi everyone,
My name is Apex Poudel. I’ve been reviewing and contributing to the App Inventor codebase for some time, and I’ve also been a long-time App Inventor user (built a few apps + participated in an App Inventor hackathon a while back), so it’s been great to finally contribute on the dev side.
I had a couple of quick questions I wanted to clarify:
a. While reviewing a recent PR, I noticed that a few unrelated files (e.g., local documentation/build artifacts) were included alongside the actual feature changes. I left a comment asking whether such files should be excluded, but wasn’t sure if there’s an established convention around this.From the contribution guidelines, my understanding is that PRs should ideally stay scoped to the functional change being proposed. Could someone confirm whether auxiliary artifacts ( local build outputs, generated files, or environment specific artifacts) are expected to be excluded, or if there are cases where including them is acceptable?
b. Additionally, while exploring the codebase more deeply, I’ve come across a few minor technical inconsistencies, for example:
i. variable or constant naming mismatches across related components
ii. comments or identifiers whose semantics no longer align with current behavior
iii.small logic inconsistencies that don’t cause failures but could affect maintainability or readability
Would it be appropriate for me to submit small, focused PRs addressing these kinds of issues as I encounter them, or is there a preferred workflow ( batching changes, opening an issue first, etc.)?
just want to make sure I’m aligned with how things are usually done before moving ahead.
Thanks,
Apex.