Tymoteusz Czech
6d0e32810c
fix: empty paginated table state ( #5685 )
...
Table placeholder should be visible if search query returns no data.
2023-12-20 14:11:21 +00:00
Jaanus Sellin
8e7e389d1d
fix: context updated event now does stores correct fields ( #5705 )
2023-12-20 15:57:17 +02:00
Mateusz Kwasniewski
f3ca4f0c54
chore: upgrading vite to newer version ( #5703 )
2023-12-20 14:48:18 +01:00
andreas-unleash
0f8a6661a8
Feat: allow rescheduling of failed scheduled cr ( #5702 )
...
Allows for rescheduling failed scheduled requests
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
2023-12-20 15:19:23 +02:00
Jaanus Sellin
bb5b322475
fix: now project overview has skeleton instead of placeholders ( #5696 )
...
Removed `ref` dependency from `useLoading` hook, it was being overly
reactive and breaking skeleton.
2023-12-20 14:59:41 +02:00
Nuno Góis
1a79921a38
chore: incoming webhook events ( #5693 )
...
https://linear.app/unleash/issue/2-1748/create-new-incoming-webhook-events
Adds new events for write operations on incoming webhooks and their
tokens.
2023-12-20 11:48:25 +00:00
Gastón Fournier
218d5625fb
chore: unify build and build PRs workflow ( #5570 )
...
## About the changes
Our build and build_prs workflows are almost the same with some minor
details:
1. **Build** also builds the frontend, but **PR Build** does not by
specifying `--ignore-scripts`
1. **Build PR** uploads test results: Upload test report to build. We'll
ignore this when building on main
1. **Build PR** just builds the backend (reason why the build is much
faster: 50s vs ~5m). We have a workflow for building frontend PRs, we'd
be removing the build frontend from the build on main, but we're already
exercising that to upload to dockerhub:
![image](https://github.com/Unleash/unleash/assets/455064/36f5a892-24dc-4de2-91bd-8e3419757b0d )
These are the main differences:
![image](https://github.com/Unleash/unleash/assets/455064/837b1ea4-305d-4472-b903-aeed7f3f3e7f )
This PR unifies the two workflows into one
2023-12-20 11:44:49 +01:00
Mateusz Kwasniewski
7be0c55d39
fix: move paginated table into isolation context ( #5694 )
2023-12-20 10:47:22 +01:00
renovate[bot]
53eb1f6b92
chore(deps): update react-router monorepo to v6.20.1 ( #5536 )
...
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg )](https://renovatebot.com )
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [react-router](https://togithub.com/remix-run/react-router )
([source](https://togithub.com/remix-run/react-router/tree/HEAD/packages/react-router ))
| [`6.16.0` ->
`6.20.1`](https://renovatebot.com/diffs/npm/react-router/6.16.0/6.20.1 )
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/react-router/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router/6.16.0/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router/6.16.0/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
| [react-router-dom](https://togithub.com/remix-run/react-router )
([source](https://togithub.com/remix-run/react-router/tree/HEAD/packages/react-router-dom ))
| [`6.16.0` ->
`6.20.1`](https://renovatebot.com/diffs/npm/react-router-dom/6.16.0/6.20.1 )
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/react-router-dom/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router-dom/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router-dom/6.16.0/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router-dom/6.16.0/6.20.1?slim=true )](https://docs.renovatebot.com/merge-confidence/ )
|
---
### Release Notes
<details>
<summary>remix-run/react-router (react-router)</summary>
###
[`v6.20.1`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6201 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.20.0...react-router@6.20.1 )
##### Patch Changes
- Revert the `useResolvedPath` fix for splat routes due to a large
number of applications that were relying on the buggy behavior (see
[https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329 ](https://togithub.com/remix-run/react-router/issues/11052#issuecomment-1836589329 )).
We plan to re-introduce this fix behind a future flag in the next minor
version.
([#​11078](https://togithub.com/remix-run/react-router/pull/11078 ))
- Updated dependencies:
- `@remix-run/router@1.13.1`
###
[`v6.20.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6200 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.19.0...react-router@6.20.0 )
##### Minor Changes
- Export the `PathParam` type from the public API
([#​10719](https://togithub.com/remix-run/react-router/pull/10719 ))
##### Patch Changes
- Fix bug with `resolveTo` in splat routes
([#​11045](https://togithub.com/remix-run/react-router/pull/11045 ))
- This is a follow up to
[#​10983](https://togithub.com/remix-run/react-router/pull/10983 )
to handle the few other code paths using `getPathContributingMatches`
- This removes the `UNSAFE_getPathContributingMatches` export from
`@remix-run/router` since we no longer need this in the
`react-router`/`react-router-dom` layers
- Updated dependencies:
- `@remix-run/router@1.13.0`
###
[`v6.19.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6190 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.18.0...react-router@6.19.0 )
##### Minor Changes
- Add `unstable_flushSync` option to
`useNavigate`/`useSumbit`/`fetcher.load`/`fetcher.submit` to opt-out of
`React.startTransition` and into `ReactDOM.flushSync` for state updates
([#​11005](https://togithub.com/remix-run/react-router/pull/11005 ))
- Remove the `unstable_` prefix from the
[`useBlocker`](https://reactrouter.com/en/main/hooks/use-blocker ) hook
as it's been in use for enough time that we are confident in the API. We
do not plan to remove the prefix from `unstable_usePrompt` due to
differences in how browsers handle `window.confirm` that prevent React
Router from guaranteeing consistent/correct behavior.
([#​10991](https://togithub.com/remix-run/react-router/pull/10991 ))
##### Patch Changes
- Fix `useActionData` so it returns proper contextual action data and
not *any* action data in the tree
([#​11023](https://togithub.com/remix-run/react-router/pull/11023 ))
- Fix bug in `useResolvedPath` that would cause `useResolvedPath(".")`
in a splat route to lose the splat portion of the URL path.
([#​10983](https://togithub.com/remix-run/react-router/pull/10983 ))
- ⚠️ This fixes a quite long-standing bug specifically for `"."` paths
inside a splat route which incorrectly dropped the splat portion of the
URL. If you are relative routing via `"."` inside a splat route in your
application you should double check that your logic is not relying on
this buggy behavior and update accordingly.
- Updated dependencies:
- `@remix-run/router@1.12.0`
###
[`v6.18.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6180 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.17.0...react-router@6.18.0 )
##### Patch Changes
- Fix the `future` prop on `BrowserRouter`, `HashRouter` and
`MemoryRouter` so that it accepts a `Partial<FutureConfig>` instead of
requiring all flags to be included.
([#​10962](https://togithub.com/remix-run/react-router/pull/10962 ))
- Updated dependencies:
- `@remix-run/router@1.11.0`
###
[`v6.17.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6170 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router@6.16.0...react-router@6.17.0 )
##### Patch Changes
- Fix `RouterProvider` `future` prop type to be a
`Partial<FutureConfig>` so that not all flags must be specified
([#​10900](https://togithub.com/remix-run/react-router/pull/10900 ))
- Updated dependencies:
- `@remix-run/router@1.10.0`
</details>
<details>
<summary>remix-run/react-router (react-router-dom)</summary>
###
[`v6.20.1`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6201 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.20.0...react-router-dom@6.20.1 )
##### Patch Changes
- Revert the `useResolvedPath` fix for splat routes due to a large
number of applications that were relying on the buggy behavior (see
[https://github.com/remix-run/react-router/issues/11052#issuecomment-1836589329 ](https://togithub.com/remix-run/react-router/issues/11052#issuecomment-1836589329 )).
We plan to re-introduce this fix behind a future flag in the next minor
version.
([#​11078](https://togithub.com/remix-run/react-router/pull/11078 ))
- Updated dependencies:
- `react-router@6.20.1`
- `@remix-run/router@1.13.1`
###
[`v6.20.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6200 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.19.0...react-router-dom@6.20.0 )
##### Minor Changes
- Export the `PathParam` type from the public API
([#​10719](https://togithub.com/remix-run/react-router/pull/10719 ))
##### Patch Changes
- Updated dependencies:
- `react-router@6.20.0`
- `@remix-run/router@1.13.0`
###
[`v6.19.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6190 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.18.0...react-router-dom@6.19.0 )
##### Minor Changes
- Add `unstable_flushSync` option to
`useNavigate`/`useSumbit`/`fetcher.load`/`fetcher.submit` to opt-out of
`React.startTransition` and into `ReactDOM.flushSync` for state updates
([#​11005](https://togithub.com/remix-run/react-router/pull/11005 ))
- Allow `unstable_usePrompt` to accept a `BlockerFunction` in addition
to a `boolean`
([#​10991](https://togithub.com/remix-run/react-router/pull/10991 ))
##### Patch Changes
- Fix issue where a changing fetcher `key` in a `useFetcher` that
remains mounted wasn't getting picked up
([#​11009](https://togithub.com/remix-run/react-router/pull/11009 ))
- Fix `useFormAction` which was incorrectly inheriting the `?index`
query param from child route `action` submissions
([#​11025](https://togithub.com/remix-run/react-router/pull/11025 ))
- Fix `NavLink` `active` logic when `to` location has a trailing slash
([#​10734](https://togithub.com/remix-run/react-router/pull/10734 ))
- Updated dependencies:
- `react-router@6.19.0`
- `@remix-run/router@1.12.0`
###
[`v6.18.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6180 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.17.0...react-router-dom@6.18.0 )
##### Minor Changes
- Add support for manual fetcher key specification via `useFetcher({
key: string })` so you can access the same fetcher instance from
different components in your application without prop-drilling
([RFC](https://togithub.com/remix-run/remix/discussions/7698 ))
([#​10960](https://togithub.com/remix-run/react-router/pull/10960 ))
- Fetcher keys are now also exposed on the fetchers returned from
`useFetchers` so that they can be looked up by `key`
- Add `navigate`/`fetcherKey` params/props to `useSumbit`/`Form` to
support kicking off a fetcher submission under the hood with an
optionally user-specified `key`
([#​10960](https://togithub.com/remix-run/react-router/pull/10960 ))
- Invoking a fetcher in this way is ephemeral and stateless
- If you need to access the state of one of these fetchers, you will
need to leverage `useFetcher({ key })` to look it up elsewhere
##### Patch Changes
- Adds a fetcher context to `RouterProvider` that holds completed
fetcher data, in preparation for the upcoming future flag that will
change the fetcher persistence/cleanup behavior
([#​10961](https://togithub.com/remix-run/react-router/pull/10961 ))
- Fix the `future` prop on `BrowserRouter`, `HashRouter` and
`MemoryRouter` so that it accepts a `Partial<FutureConfig>` instead of
requiring all flags to be included.
([#​10962](https://togithub.com/remix-run/react-router/pull/10962 ))
- Updated dependencies:
- `@remix-run/router@1.11.0`
- `react-router@6.18.0`
###
[`v6.17.0`](https://togithub.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6170 )
[Compare
Source](https://togithub.com/remix-run/react-router/compare/react-router-dom@6.16.0...react-router-dom@6.17.0 )
##### Minor Changes
- Add experimental support for the [View Transitions
API](https://developer.mozilla.org/en-US/docs/Web/API/ViewTransition )
via `document.startViewTransition` to enable CSS animated transitions on
SPA navigations in your application.
([#​10916](https://togithub.com/remix-run/react-router/pull/10916 ))
The simplest approach to enabling a View Transition in your React Router
app is via the new `<Link unstable_viewTransition>` prop. This will
cause the navigation DOM update to be wrapped in
`document.startViewTransition` which will enable transitions for the DOM
update. Without any additional CSS styles, you'll get a basic cross-fade
animation for your page.
If you need to apply more fine-grained styles for your animations, you
can leverage the `unstable_useViewTransitionState` hook which will tell
you when a transition is in progress and you can use that to apply
classes or styles:
```jsx
function ImageLink(to, src, alt) {
let isTransitioning = unstable_useViewTransitionState(to);
return (
<Link to={to} unstable_viewTransition>
<img
src={src}
alt={alt}
style={{
viewTransitionName: isTransitioning ? "image-expand" : "",
}}
/>
</Link>
);
}
```
You can also use the `<NavLink unstable_viewTransition>` shorthand which
will manage the hook usage for you and automatically add a
`transitioning` class to the `<a>` during the transition:
```css
a.transitioning img {
view-transition-name: "image-expand";
}
```
```jsx
<NavLink to={to} unstable_viewTransition>
<img src={src} alt={alt} />
</NavLink>
```
For an example usage of View Transitions with React Router, check out
[our fork](https://togithub.com/brophdawg11/react-router-records ) of the
[Astro Records](https://togithub.com/Charca/astro-records ) demo.
For more information on using the View Transitions API, please refer to
the [Smooth and simple transitions with the View Transitions
API](https://developer.chrome.com/docs/web-platform/view-transitions/ )
guide from the Google Chrome team.
Please note, that because the `ViewTransition` API is a DOM API, we now
export a specific `RouterProvider` from `react-router-dom` with this
functionality. If you are importing `RouterProvider` from
`react-router`, then it will not support view transitions.
([#​10928](https://togithub.com/remix-run/react-router/pull/10928 )
##### Patch Changes
- Log a warning and fail gracefully in `ScrollRestoration` when
`sessionStorage` is unavailable
([#​10848](https://togithub.com/remix-run/react-router/pull/10848 ))
- Updated dependencies:
- `@remix-run/router@1.10.0`
- `react-router@6.17.0`
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, Automerge - At any time (no
schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/ ). View
repository job log
[here](https://developer.mend.io/github/Unleash/unleash ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44MS4zIiwidXBkYXRlZEluVmVyIjoiMzcuODcuMiIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-12-20 10:10:10 +01:00
Fredrik Strand Oseberg
5a263ee35c
Feat/new strategy configuration tests ( #5692 )
...
Does what it says
2023-12-20 09:16:45 +01:00
Thomas Heartman
a9bf831759
Update publish-new-version.yaml ( #5691 )
...
Add more details about the how the version should be formatted.
When trying to run this workflow, I'm always very unsure whether the
version should be prepended with a `v` or not. This should be clearly
stated in the description. If it doesn't matter, that should also be
stated explicitly.
Updated the texts after talking to @chriswk and making a release.
2023-12-20 08:15:22 +01:00
Ivar Conradi Østhus
637b1b05e0
docs: Validate vercel.docs and build
2023-12-19 20:16:14 +01:00
Jaanus Sellin
c979e687ca
fix: remove extra call to features on project load ( #5690 )
...
Currently EnableEnvironmentDialog was loaded even if no feature was
touched. Now it will only load, if feature toggle was selected.
2023-12-19 21:03:24 +02:00
Tymoteusz Czech
dce91b0e90
fix: pagination and column width
2023-12-19 16:24:43 +01:00
Mateusz Kwasniewski
8306073e1f
feat: keep filter order ( #5688 )
2023-12-19 15:35:39 +01:00
andreas-unleash
b933a03e8a
fix: conflict email naming bug - cleanup files ( #5683 )
...
Fixes name bug in template folder
Removes/cleans up the plain html files
Relates to #
[1-1605](https://linear.app/unleash/issue/1-1605/send-an-email-to-the-user-whose-scheduled-changes-can-no-longer-be )
Closes #
[1-1726](https://linear.app/unleash/issue/1-1726/manual-testing )
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
2023-12-19 16:01:16 +02:00
Nuno Góis
c0bc2d9b68
fix: prevent banner from crashing with invalid variant ( #5686 )
...
https://linear.app/unleash/issue/2-1760/prevent-banner-from-crashing-when-set-with-an-invalid-variant
This prevents the banner from crashing when set with an invalid variant.
Instead, it default its styles to the default variant, which is `info`.
Also adds tests to validate our assumptions.
2023-12-19 13:09:40 +00:00
Tymoteusz Czech
8388700f76
fix: project features batch actions refetch ( #5680 )
...
Reload paginated features on project overview after batch action.
2023-12-19 14:46:06 +02:00
Jaanus Sellin
42943ada75
fix: now history is only shown to search bars that have id to save hi… ( #5684 )
2023-12-19 14:20:10 +02:00
David Leek
33f82daa8c
chore: add migration that renames new created_by columns ( #5681 )
...
## About the changes
Replaces #5616
Renamed newly added `created_by` columns to `created_by_user_id` for
these tables:
features
feature_tag
feature_strategies
feature_types
role_permission
role_user
roles
users
api_tokens
2023-12-19 13:14:15 +01:00
Gastón Fournier
061bd7ef32
chore: use semver compatible version ( #5678 )
...
## About the changes
Replicate the change made to respect semver
2023-12-19 12:47:03 +01:00
Jaanus Sellin
8e09f08a05
feat: rebrand feature toggle list as search ( #5675 )
2023-12-19 13:42:14 +02:00
David Leek
5603e8683d
chore: list users and groups under each role in projectaccessadded event ( #5581 )
...
## About the changes
Changes the project access added event to list all users and groups
added to each role instead of in root event.
2023-12-19 10:16:17 +01:00
Mateusz Kwasniewski
7800d9d1b4
feat: export all features in project ( #5677 )
2023-12-19 08:57:10 +01:00
Ivar Conradi Østhus
1043efd89f
fix: use node v18.19.0 ( #5662 )
2023-12-18 19:57:24 +01:00
Nuno Góis
138d303da4
chore: rename secret to token in incoming_webhook_tokens ( #5679 )
...
Renames `secret` to `token` in `incoming_webhook_tokens` for
consistency. This table is not being used yet, so this should be a very
safe change.
2023-12-18 17:11:59 +00:00
Tymoteusz Czech
b2c31a3bd3
fix: column visibility ( #5676 )
...
- always show favorites and selection
- reset local storage columns cache
2023-12-18 16:24:39 +01:00
Ivar Conradi Østhus
9e95a6547e
docs: add vercel.json
2023-12-18 15:34:25 +01:00
Nuno Góis
5f975bbad7
chore: incoming webhooks and tokens migration ( #5670 )
...
https://linear.app/unleash/issue/2-1699/db-create-migration-for-a-new-incoming-webhooks-table
Adds a migration that creates 2 tables:
- `incoming_webhooks`
- `incoming_webhook_tokens`
2023-12-18 13:22:28 +00:00
Mateusz Kwasniewski
e380d28924
feat: up and down arrow navigation for filter items ( #5673 )
2023-12-18 14:13:32 +01:00
andreas-unleash
75bdd73c15
feat: add plausible tracking to scheduling ( #5668 )
...
Adds plausible tracking with actions:
- scheduled-created
- scheduled-updated
- scheduled-rejected
- scheduled-applied
Closes #
[1-1630](https://linear.app/unleash/issue/1-1630/add-plausible-metrics )
---------
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
2023-12-18 15:06:58 +02:00
Paulo Miranda
fd34f35e0e
feat: add reset password to user manager ( #5580 )
...
## About the changes
This PR adds a reset password functionality to user table (only available to admins). This makes it possible to reset passwords without configuring the email service.
![Screenshot from 2023-12-10
20-41-22](https://github.com/Unleash/unleash/assets/32435715/0209525a-4f3a-4998-b9de-7299469e1a68 )
![Screenshot from 2023-12-16
16-40-36](https://github.com/Unleash/unleash/assets/32435715/556e324c-c0b0-4bb9-b2b5-3bd653f4d329 )
![Screenshot from 2023-12-16
16-40-48](https://github.com/Unleash/unleash/assets/32435715/b0249e9d-9e1a-4cfe-a5ee-0ab22f45ce28 )
---------
Co-authored-by: Ivar Conradi Østhus <ivarconr@gmail.com>
Co-authored-by: Thomas Heartman <thomasheartman+github@gmail.com>
2023-12-18 13:54:04 +01:00
Mateusz Kwasniewski
c5b3058890
fix: date filter item missing key ( #5674 )
2023-12-18 13:51:27 +01:00
Jaanus Sellin
d0facc7101
fix: adjust page limit normalization ( #5672 )
2023-12-18 14:33:45 +02:00
Jaanus Sellin
3b635132f9
feat: enable sorting by project ( #5671 )
2023-12-18 14:33:38 +02:00
Jaanus Sellin
4af0abc6c2
fix: increase page size in backend to 100 ( #5669 )
2023-12-18 14:18:05 +02:00
Nuno Góis
00ed539c19
Revert "chore: incoming webhooks and tokens migration"
...
This reverts commit 695474576e
.
2023-12-18 11:47:04 +00:00
Nuno Góis
695474576e
chore: incoming webhooks and tokens migration
2023-12-18 11:44:29 +00:00
Mateusz Kwasniewski
6bf54a2f24
feat: keyboard navigation filter item ( #5667 )
2023-12-18 12:36:00 +01:00
Mateusz Kwasniewski
5ba588f59a
feat: Multi highlighter ( #5666 )
2023-12-18 10:58:07 +01:00
andreas-unleash
7fdd720aa3
feat: show failure in cr overview ( #5660 )
...
Show failure reason in change request overview
Closes
[1-1769](https://linear.app/unleash/issue/1-1769/add-reason-and-icon-to-change-request-overview )
<img width="771" alt="Screenshot 2023-12-15 at 10 37 03"
src="https://github.com/Unleash/unleash/assets/104830839/898b6ac9-bd44-442f-92a4-9b4d5754fea7 ">
---------
Signed-off-by: andreas-unleash <andreas@getunleash.ai>
2023-12-18 11:37:56 +02:00
Jaanus Sellin
f4268347da
fix: last seen now sorts nulls last ( #5664 )
...
Two changes were needed to sort better
1. Since we are still using `last seen` from `features` table for
backwards compatibility, we needed to add it to sort condition.
2. Nulls break the order, so now sorting nulls as last.
2023-12-18 10:36:50 +02:00
Jaanus Sellin
2da919fee9
fix: disable sort ( #5665 )
...
'
2023-12-18 10:25:10 +02:00
Mateusz Kwasniewski
cc01971ff0
feat: update message with no feature toggles ( #5663 )
2023-12-18 09:05:58 +01:00
Thomas Heartman
ab2281d7e7
fix: make username nullable in user-schema ( #5656 )
...
I noticed I was getting warnings logged in my local instance when
visiting the users page (`/admin/users`)
```json
{
"schema": "#/components/schemas/publicSignupTokensSchema",
"errors": [
{
"instancePath": "/tokens/0/users/0/username",
"schemaPath": "#/components/schemas/userSchema/properties/username/type",
"keyword": "type",
"params": {
"type": "string"
},
"message": "must be string"
}
]
}
```
It was complaining because one of my users doesn't have a username, so
the value returned from the API was:
```json
{
"users": [
{
"id": 2,
"name": "2mas",
"username": null
}
]
}
```
This adjustment fixes that oversight by allowing `null` values for the
username.
2023-12-16 08:28:22 +01:00
Pedro Papadopolis
24c2a70138
feat: Make compression middleware optional ( #5306 )
...
## Why
Currently AWS API Gateway doesn't have compression enabled by default,
this PR will make it easier to for example deploy Unleash over to AWS
Lambda without further configuration in API Gateway, frameworks like
Serverless requires a bit more work to set up compression and some times
one might not need compression at all.
## How
Create a new config flag called `disableCompression` which will not
include `compression` middleware in express' instance when set as true.
2023-12-16 08:06:26 +01:00
Drew Gorton
d41e86771f
Add Banner for New Years Community Party ( #5661 )
...
Link to website signup page
2023-12-16 07:36:08 +01:00
Tymoteusz Czech
50ff36cbce
feat: feature table tags ( #5659 )
...
- tags on project overview
- refactor of tags cell
2023-12-15 16:22:19 +01:00
Mateusz Kwasniewski
d429f51cbd
feat: filter chips icons ( #5658 )
2023-12-15 13:42:09 +00:00
Fredrik Strand Oseberg
864ae4530b
Feat/new strategy configuration header ( #5655 )
...
This PR adds more information to the header of the strategy according to
the new designs:
<img width="1298" alt="Skjermbilde 2023-12-15 kl 13 31 26"
src="https://github.com/Unleash/unleash/assets/16081982/73a3bc6b-c78b-4f24-b9f3-8a4b2c14e39c ">
2023-12-15 14:09:47 +01:00