-
Notifications
You must be signed in to change notification settings - Fork 970
feat: adds initial API files for notices endpoint #2093
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
chore: adds basic api file and test Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
Signed-off-by: Marcos Iglesias <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM so far, thanks!
@@ -207,10 +207,19 @@ export enum NoticeSeverity { | |||
WARNING = 'warning', | |||
ALERT = 'alert', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense for the highest level to be called 'error' instead of 'alert'? not sure if 'alert' conveys to me that it would be a higher severity over a warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. However, that would be a breaking change at this moment (this is from the currently working notices feature)
* chore: adds fixture data for notices API chore: adds basic api file and test Signed-off-by: Marcos Iglesias <[email protected]> * chore: normalizes initialState for tags and badges Signed-off-by: Marcos Iglesias <[email protected]> * feat: adds notices sagas and related tests Signed-off-by: Marcos Iglesias <[email protected]> * chore: adds action tests Signed-off-by: Marcos Iglesias <[email protected]> * chore: adds reducer and tests Signed-off-by: Marcos Iglesias <[email protected]> * chore: updated rootReducer and rootSaga Signed-off-by: Marcos Iglesias <[email protected]> * chore: adds STATUS_CODES constants Signed-off-by: Marcos Iglesias <[email protected]> * chore: rolls out STATUS_CODES constants Signed-off-by: Marcos Iglesias <[email protected]> * chore: adds copyright messages Signed-off-by: Marcos Iglesias <[email protected]> * fix: fixes type issues Signed-off-by: Marcos Iglesias <[email protected]> * chore: using other data builder options to increase coverage Signed-off-by: Marcos Iglesias <[email protected]> * chore: move into testDataBuilder file and exclude from test coverage Signed-off-by: Marcos Iglesias <[email protected]> --------- Signed-off-by: Marcos Iglesias <[email protected]> Signed-off-by: Ben Dye <[email protected]>
Summary of Changes
Adds reducer, actions, sagas and endpoints for the WIP notices endpoint
Creates STATUS_CODES constants for all status codes
Updated jest.config to not use testDataBuilder.ts files on test coverage report
Tests
Added tests
Related to the stretch goals on https://github.com/amundsen-io/rfcs/blob/master/rfcs/029-resource-notices.md