-
Notifications
You must be signed in to change notification settings - Fork 1
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
Release v0.0.3 #23
Merged
Merged
Release v0.0.3 #23
Conversation
This file contains 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
- @BabylonJS:4.1.0-beta.9 - @types/node:12.12.16
- coordinates get always rounded down
- Test suite failed to run - Call retries were exceeded at ChildProcessWorker.initialize() - jest-community/vscode-jest#486 (comment)
- but negative position
- to run in Jest tests within WebStorm - nrwl/nx#1439 (comment)
- to run in Jest tests within WebStorm with SCSS imports in component
* feat(ui): add `Storybook` * feat(ui): add `Storybook` e2e test * doc(ui): how to watch e2e * build(dep): update storybook to `v5.3.6` * build(dep): back to storybook `v5.3.2` due to: - info => Using angular project 'frontend' for configuring Storybook. * build(dep): back to storybook `v5.3.6` since it works * test(ui-e2e): open/close `menu-bar`
* ci(storybook): build storybook * ci(storybook): move `frontend e2e` step down * ci(storybook): store storybook & deploy to gh-pages * ci(storybook): extract git(hub) configs * ci(storybook): extract deploy to gh-pages * ci(storybook): change to `test-results` folder & use `junit` reporter * ci(storybook): run `ui-e2e` and store test-results & artifacts * ci(storybook): run `ui-e2e` only on `master` & `develop`
* feat(frontend): dispatch paint-voxel action * feat(frontend): set voxel on paint * feat(frontend): finish renaming `addVoxel` to `setVoxel` * feat(frontend): save old/new values and undo/redo painting * refactor(frontend): s/positions/coord * refactor(frontend): fix prettier issue
- `ng update @angular/cli @angular/core`
* feat(ui): color-dialog * refactor(ui): always open dialog in story * refactor(ui): flatten config to just menus & type safety in story * feat(ui): pass colors to color-dialog * refactor(ui): make data & return value type-safe. * refactor(ui): extract interface `UiColorDialogData` * refactor(ui): extract open into `UiColorDialogService` * test(ui): s/UiMenuBarConfig/UiMenuBarMenu * refactor(ui): provide `selectedColorIndex`
* feat(frontend): use color-dialog * refactor(ui): s/draggable-dialog/color-dialog * feat(frontend): open (empty) color-dialog * feat(frontend): provide some first colors * feat(frontend): use effects to open color-dialog * feat(frontend): use effects to set selected color in store * feat(frontend): temp. consider just `color.r` * feat(frontend): save colors and selected-index * refactor(frontend): move `tool.model.ts` to `model` (put in lib later) * feat(frontend): `intToRgba` & `rgbaToInt` * refactor(frontend): s/model/value * refactor(frontend): use `Rgba` and `rgbaToInt` to set voxel in grid * refactor(frontend): provide selector for retrieving CSS colors * refactor(frontend): move comment `Front` * refactor(vdb): define all colors * refactor(frontend): fix prettier * test(frontend): import `OptionsPanelModule` * refactor(frontend): prettier * refactor(ui): `forceDepthWrite` for transparent cubes - there are still some artifacts (seeing through cubes behind) * refactor(ui): use `rgba` to set initial voxel at [0, 0, 0] * test(frontend): provide stub component in `AppComponent` test * test(frontend): provide `initialMockState` * test(frontend): mock & expect proper `Rgba` values * test(ui): fix type of dialog result (`UiColorDialogColor` to `number`)
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.
No description provided.