gitar-bot[bot]
4615ff40ce
[Gitar] Cleaning up stale flag: resourceLimits with value true ( #7964 )
...
[](https://gitar.co )
---
This automated PR was generated by [Gitar](https://gitar.co ). View
[docs](https://gitar.co/docs ).
---------
Co-authored-by: Gitar <noreply@gitar.co>
Co-authored-by: Thomas Heartman <thomas@getunleash.io>
2024-08-22 13:20:53 +02:00
Mateusz Kwasniewski
e7d07486a1
feat: limit segments component ( #7553 )
2024-07-08 09:03:08 +02:00
Christopher Kolstad
53354224fc
chore: Bump biome and configure husky ( #6589 )
...
Upgrades biome to 1.6.1, and updates husky pre-commit hook.
Most changes here are making type imports explicit.
2024-03-18 13:58:05 +01:00
Thomas Heartman
dba1c90db8
Feat: show change request data on segment project usage page ( #5410 )
...
Show usage in change requests if that'd cause you to not be able to move
the segment into a project.
- [x] ~Relies on changes from #5407 (and #5405 , #5406 ) to go through
first.~

2023-11-28 10:01:56 +01:00
Nuno Góis
4167a60588
feat: biome lint frontend ( #4903 )
...
Follows up on https://github.com/Unleash/unleash/pull/4853 to add Biome
to the frontend as well.

Added a few `biome-ignore` to speed up the process but we may want to
check and fix them in the future.
2023-10-02 13:25:46 +01:00
Jaanus Sellin
2bf995e731
feat: context/segment usage private ( #4826 )
2023-09-25 15:50:44 +03:00
Nuno Góis
5c9bf7b0e9
refactor: misc cleanups ( #4022 )
...
Misc cleanups of unused imports / variables.
2023-06-21 15:08:52 +01:00
Gastón Fournier
ab4a6f5c92
chore: GA project specific segments ( #3583 )
...
## About the changes
General availability of project-specific segments
Now new permissions can be assigned to non-admin users to allow them to
create segments specifically bounded to a project (note that unique
naming restriction applies across projects, this limitation can be
lifted later).

This enables a section in the project configuration to add
project-specific segments

2023-04-21 10:25:40 +02:00
Nuno Góis
27d48b3437
Feat segments project safeguards ( #3359 )
...
https://linear.app/unleash/issue/2-811/ability-to-move-project-specific-segments

Provides some safeguards to project-specific segments when managing them
on a global level (segments page):
- You can always promote a segment to global;
- You can't specify a project if the segment is currently in use in
multiple projects;
- You can't specify a different project if the segment is currently
already in use in a project;
2023-03-21 20:28:43 +00:00
Nuno Góis
292d6a7f60
feat: implement project-scoped segments in project settings ( #3335 )
...
https://linear.app/unleash/issue/2-743/have-a-project-specific-configuration-section

Adds the "segments" option to project settings, providing the usual CRUD
operations but scoped to the specific project.
2023-03-17 08:23:27 +00:00
Nuno Góis
fe1e3566ee
fix: assume undefined instead of null on segment project ( #3304 )
...
Assume `undefined` instead of `null` for project in terms of interfacing
with segments: If the `project` field is not present, that means that it
is not set, which means we're dealing with a "global" segment. If we
want to unset `project` and make a segment global, we simply don't send
the `project` property on our PUT method.
2023-03-13 10:25:48 +00:00
Nuno Góis
ff7185fe5b
feat: allow adding project to segment ( #3290 )
...
https://linear.app/unleash/issue/2-741/add-project-dropdown-into-creation-of-segments
Allows users to bind a segment to a project when creating or editing a
segment.
<img width="1051" alt="image"
src="https://user-images.githubusercontent.com/14320932/224103846-1fe1f849-496c-4a77-9831-53bcb36f822e.png ">
2023-03-10 08:16:54 +00:00
sjaanus
b631618532
Makestyles refactor #7/1 ( #2805 )
2023-01-03 16:30:59 +02:00