@bigbinary/neeto-filters-frontend 3.2.0 → 3.3.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -10,6 +10,7 @@ The `neeto-filters-nano` manages filters across neeto products. The nano export
10
10
  - [Installation](#installation-1)
11
11
  - [Components](#components)
12
12
  2. [Instructions for Publishing](#instructions-for-publishing)
13
+ 3. [Releasing beta versions](#releasing-beta-versions)
13
14
 
14
15
  # Development with Host Application
15
16
  ## Engine
@@ -125,6 +126,7 @@ export default App;
125
126
  - `childrenKeys`: The list of keys which has to be cleared from url during clear filters operation.
126
127
  - `entity`: The entity associated with the filters.
127
128
  - `defaultSegmentName`: The name of segment which results all entities without applying any filter. Default name is "All results".
129
+ - `customFilters`: To specify the custom components specific to the host application. This should be same as `children` passed to the `Filters` component.
128
130
 
129
131
  All these props must be same as that passed to the `Filters` component. The
130
132
  option to save filters as segments will be enabled only when the entity prop is
@@ -183,6 +185,8 @@ export default App;
183
185
  - `entity`: The entity associated with the segments.
184
186
  - `setIsPaneOpen`: To trigger the isOpen state of the filters pane.
185
187
  - `defaultSegmentName`: The name of segment which results all entities without applying any filter. Default name is "All results".
188
+ - `customFilters`: To specify the custom components specific to the host application. This should be same as `children` passed to the `Filters` component.
189
+ - `childrenKeys`: The list of keys which has to be cleared from url during clear filters operation.
186
190
 
187
191
  The "columns" prop must be same as that passed to the `Filters` component.
188
192
 
@@ -450,3 +454,21 @@ this case, all the users whose email address contains `bigbinary` in the
450
454
 
451
455
  # Instructions for Publishing
452
456
  Consult the [building and releasing packages](https://neeto-engineering.neetokb.com/articles/building-and-releasing-packages) guide for details on how to publish.
457
+
458
+ # Releasing beta versions
459
+
460
+ - Push the changes to a target branch for releasing beta version.
461
+ - Update the package version to `{latest-version}-beta` (if `1.2.34` is the
462
+ current latest version, it will be `1.2.34-beta`) in the target branch for
463
+ beta release.
464
+ - [Draft a new release](https://github.com/bigbinary/neeto-filters-nano/releases/new)
465
+ from the repo with the target branch.
466
+ - Add a new tag and title in the format: version prefixed with `v`, eg:
467
+ `v1.2.34-beta`.
468
+ - Generate release notes.
469
+ - Set the release as a pre-release and publish the release.
470
+ <img width="640" alt="image" src="https://private-user-images.githubusercontent.com/22348659/292095447-8bcb83f3-dc52-46f8-98f9-a388df33abf2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDc0NTU4MDcsIm5iZiI6MTcwNzQ1NTUwNywicGF0aCI6Ii8yMjM0ODY1OS8yOTIwOTU0NDctOGJjYjgzZjMtZGM1Mi00NmY4LTk4ZjktYTM4OGRmMzNhYmYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMjA5VDA1MTE0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTljYjQwOGMwYTY3ZjhmZGM4N2VjNmMwMjhlYTIxY2MzYTNmZjZhMDRmZDU1OWZjMzkzNmVmZmFhNDVlZTNmMDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.GdDk-fZIuLoZhqSdWJkvvU8l1_N-lwQEgWm5ttc7Ebs">
471
+
472
+ If we are releasing a beta version to a product, we have to inform the
473
+ compliance team as well to avoid overwriting the version with latest version on
474
+ the next compliance release.
@@ -4,6 +4,7 @@
4
4
  "clearFilters": "Clear filters",
5
5
  "columns": "Columns",
6
6
  "delete": "Delete",
7
+ "edit": "Edit",
7
8
  "done": "Done",
8
9
  "filter": "Filter",
9
10
  "filters": "Filters",
@@ -46,21 +47,24 @@
46
47
  },
47
48
  "segments": {
48
49
  "addNewSegment": "Add new segment",
50
+ "saveAsNewSegment": "Save as new segment",
51
+ "editSegment": "Edit segment",
49
52
  "deleteAlertMessage": "You are permanently deleting the segment <strong>{{entity,anyCase}}</strong>. This can't be undone.",
50
53
  "deleteAlertTitle": "Delete segment?",
51
54
  "manageSegments": "Manage segments",
52
55
  "name": "Segment name",
53
56
  "noSegmentsFound": "No segments found",
54
57
  "saveSegment": "Save segment",
55
- "saveAsSegment": "Save as segment",
56
- "saveAsNewSegment": "Save as new segment",
58
+ "updateSegment": "Update segment",
57
59
  "searchSegments": "Search segments",
58
60
  "segmentName": "Segment name",
59
61
  "showLess": "See less",
60
62
  "showMoreNumbers": "See {{entity}} more",
61
- "updateSegment": "Update segment?",
62
- "updateSegmentMessage": "You are trying to update the current segment <strong>{{entity,anyCase}}</strong>.",
63
- "reservedNameErrorMessage": "This name is reserved. Please choose another name."
63
+ "nameIsRequired": "Segment name is required",
64
+ "reservedNameErrorMessage": "This name is reserved. Please choose another name.",
65
+ "addFilter": "Add filter",
66
+ "newFilter": "New filter",
67
+ "selectFilter": "Select filter"
64
68
  },
65
69
  "labels": {
66
70
  "keyword": "Keyword"