-
Notifications
You must be signed in to change notification settings - Fork 107
v1.2.8 #231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
v1.2.8 #231
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* fix: iife name * release: v1.2.2-alpha.0 * release: v1.2.2-alpha.1 * fix: add _EVA_IIFE_ const * feat: spine通用 * feat: spine40 * fix: comment * fix: update example * fix: const to var in spine js file * enhance d.ts * 放宽测试用例 * release: v1.2.2-type.0 Co-authored-by: aspsnd <2546697613@qq.com>
* fix: iife name * release: v1.2.2-alpha.0 * release: v1.2.2-alpha.1 * fix: add _EVA_IIFE_ const
* - feat: frame info - feat: stop at last frame * fix: use forward to stop at last frame
* add localPositino on event data * replace target with container * release: v1.2.2-type.1
* - feat: frame info - feat: stop at last frame * fix: use forward to stop at last frame * fix: sprite animation forwards
* release: v1.0.3-mini.1 * release: v1.0.3-mini.2 * add node resolve for miniprogram format * bundle resolve-loader to miniprogram format * release: v1.0.3-mini.3 * fix: export error in miniprogram adapter * update miniprogram export * fix: import PIXI from miniprogram-pixi * release: v1.0.3-mini.4 * fix: export pixi.js obj from miniprogram-pixi * release: v1.0.3-mini.5 * release: v1.0.3-mini.6 * fix: update miniprograme build * release: v1.1.2-mini.0 * release: v1.1.2-mini.1 * fix: update * release: v1.1.2-mini.2 * release: v1.1.2-mini.3 * fix: miniprogram autostart bug * fix: add property at pixi * release: v1.2.2-mini.0 * fix: * release: v1.2.2-mini.1 * fix: add pixi export * release: v1.2.2-mini.2 * release: v1.2.2-mini.3 * fix: reverse temp Co-authored-by: lidongjies <lidongjies@gmail.com>
* fix: qrcode * fix: update
* fix: iife name * release: v1.2.2-alpha.0 * release: v1.2.2-alpha.1 * fix: add _EVA_IIFE_ const * feat: spine通用 * feat: spine40 * fix: comment * fix: update example * fix: const to var in spine js file * enhance d.ts * 放宽测试用例 * release: v1.2.2-type.0 * fix:#125 * test play spine * use quene to control play action * make it current when change spine.resource Co-authored-by: fanmingfei <az8641683@163.com>
* fix: protect * fix: merge condition
* fixbug on img * fix: #170 * 删除测试样例 * fix: remove destroyed in component * fix: gameObject.id original * fix: revert lint Co-authored-by: fanmingfei <az8641683@163.com>
* add stats dw and tc panel * add stats example * Update StatsSystem.ts 修复开启监控才接入hook的问题
* fix: mask change error * fix: remove debug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: