Results 9 issues of Max Okorokov

Giving the number of issues we have about positioning, lack of resources and the fact that we're kind of rewriting popper on our own, we'll be adding `@popper/core` as a...

type: feature
needs: breaking change
type: positioning
bootstrap 5

This is an umbrella issue to allow customizing popper configuration for components. Bootstrap allows to customize certain options related to popper positioning, for example: Tooltip → https://getbootstrap.com/docs/5.1/components/tooltips/#options ``` container: selector...

type: feature
type: positioning

Currently we use clang-format for formatting only on ``` 'misc/*.ts' 'src/**/*.ts' 'e2e-app/**/*.ts' 'schematics/**/*.ts' 'playwright/**/*.ts' ``` We should migrate to Prettier. We've done a couple of tests in the past and...

type: build

Bootstrap allows changing its default popper configuration in the most generic way with the `popperConfig` option. For example, for tooltip → https://getbootstrap.com/docs/5.1/components/tooltips/#using-function-with-popperconfig Here are the available popper options → https://popper.js.org/docs/v2/constructors/#options...

type: feature
needs: design
type: positioning

Latest releases: - ng-bootstrap 10 with Angular 12 and BS 4.5 (Stable) - ng-bootstrap 11 with Angular 13 and BS 4.6 → [11.0.0](https://github.com/ng-bootstrap/ng-bootstrap/releases/tag/11.0.0) - ng-bootstrap 12 with Angular 13 and...

type: feature
breaking change
bootstrap 5

There is a new accordion component in the Bootstrap 5. We should take the opportunity to re-implement the one we have with a set of directives (same as we did...

type: feature
component: accordion
bootstrap 5

Now that we have an `NgbDateAdapter`, it might be nice to bundle a couple of default ones with the library: - [x] `NgbDateNativeAdapter` - as seen in the datepicker adapter...

type: feature
type: doc
component: datepicker

This is an aggregate issue to track zoneless support with `provideExperimentalZonelessChangeDetection()` in apps using ng-bootstrap. Please open separate issues for specific use cases, we'll reference them here. And keep in...

type: feature