… link in new tab (#631)

feat(/lib/components/button): add target to button props to be able to open a link in a new tab

Added the attribute target to the ButtonProps interface. This enables to add target="_blank" to a
button to open the associated link in a new browser tab

Thanks @Ncookiez -- All components that can have a `theme={}` should let you pass a partial theme rather than the entire object. See #646

…xt.js` (#652)

Thanks @fsioni --

* fix(themecontext): fixing `ReferenceError: window is not defined error with Next.js

The variable `userPreferenceIsDark` was initialized with a value from the window object. This was causing an error with Next because of SSR. I added the check of the window, if it's on the server side, set to white

* fix(themecontext): fixing `ReferenceError: window is not defined` error with Next.js

The variable`userPreferenceIsDark` was initialized with a value from the window object. This was
causing an error with Next because of SSR. I added the check of the window, if it's on the server
side the value is set to `false`

…634)

Closes #633

Clarifies confusing behavior for `<Progress>`.

## Breaking Changes

- `<Progress label={}>` -> `<Progress textLabel={}>`
- `<Progress labelPosition={}>` -> `<Progress progressLabelPosition={} textLabelPosition={}>`

* fix(progressbar): fix unclear label usage (#468)

* fix: add spacing to labels

* add percentage symbol to inside progress label

* add unit tests

* fix code formatting

* add unit tests

---------

Co-authored-by: Ricardo Lüders <ricardo@luders.com.br>
Co-authored-by: Conner Davis <conner@tulup.io>

Some Forms components (e.g. `<Select>`) were missing a `displayName` which can cause issues in the documentation's auto generated code previews.

* docs(component): displayName property added for components on Forms page

displayName property added for Checkbox, FileInput, Radio, RangeSlider and Select components

fix 641

* style(component): named exports added back at function declaration

fix #641

…ials` (#659) (#660)

Co-authored-by: Robert Pocklington <robert.pocklington@dubber.net>

A previous PR (#601) broke vertical positioning for modals, like `position="bottom-right"`. This reverts such changes.