Feature/assetbundle

[uitae-kim]

Description

1. Problems to solve.

AssetBundle 분리를 통한 앱 전체 용량 축소 및 메모리 최적화

2. Features to add.

AssetBundle 기능 추가
동적 로딩-언로딩 추가
기존 동적로딩 파트 AssetBundle로드로 대체

How to test

1. Builds 메뉴의 AssetBundle 빌드 테스트
2. s3에 직접 업로드 (안정성을 위해 현 버전은 CI대신 직접 업로드 선택): aws s3 cp ./AssetBundles/90.0.0 s3://9c-mobile/internal/asset-bundles/90.0.0 --recursive 등의 명령어로 수행 가능
3. 빌드 테스트 - strip engine code 옵션이 꺼져야 함, 일부 웹리퀘스트 엔진코드가 스트립됨

TODO

1. AssetBundle 다운로드 UI 필요
2. 런칭 이후 CI 작업

[pull-request-quantifier-deprecated]

This PR has 4790 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Large
Size       : +3371 -1419
Percentile : 100%

Total files changed: 286

Change summary by file extension:
.gitignore : +5 -0
.meta : +3336 -1389
.prefab : +15 -15
.mat : +12 -12
.asset : +3 -3

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ uitaekim-devcra
❌ uitae-kim
_{You have signed the CLA already but the status is still pending? Let us recheck it.}