-
Notifications
You must be signed in to change notification settings - Fork 0
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
ALS-7867 #62
base: release
Are you sure you want to change the base?
Conversation
- Deleted `DashboardDrawerList` record from the project. - Updated `DashboardDrawerController` to return a `List<DashboardDrawer>`. - Modified `DashboardDrawerService` to utilize a `List` instead of `DashboardDrawerList`. - Changed `DashboardDrawerRepository` to return `Optional<List<DashboardDrawer>>`. - Adjusted SQL join in `getDashboardDrawerRows` to use a LEFT JOIN.
- Updated `DashboardDrawerService` to use "default" layout as the fallback. - Simplified repository queries by removing materialized view checks. - Renamed methods in `DashboardDrawerRepository` for better clarity. - Removed `dashboard.layout.type` from `application-bdc.properties`. - Added unit and integration tests for `DashboardDrawerService`, `DashboardDrawerRepository`, and `DashboardDrawerController`.
@@ -13,7 +15,7 @@ public class DashboardDrawerController { | |||
private DashboardDrawerService dashboardDrawerService; | |||
|
|||
@GetMapping | |||
public ResponseEntity<DashboardDrawerList> findAll() { | |||
public ResponseEntity<List<DashboardDrawer>> findAll() { |
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.
Dumping DashboardDrawerList object in favor of using an actual list
String materializedViewSql = """ | ||
select * from dictionary_db.dict.dataset_meta_materialized_view dmmv; | ||
"""; | ||
public Optional<List<DashboardDrawer>> getDashboardDrawerRows() { |
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.
Debug log is too chatty. removing materialized views as they are not in use anyways.
@@ -15,7 +15,7 @@ public class DashboardDrawerService { | |||
private final String dashboardLayout; | |||
|
|||
@Autowired | |||
public DashboardDrawerService(DashboardDrawerRepository repository, @Value("${dashboard.layout.type}") String dashboardLayout) { | |||
public DashboardDrawerService(DashboardDrawerRepository repository, @Value("${dashboard.layout.type:default}") String dashboardLayout) { |
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.
Since there is no other implementation or requirements for other projects at the moment, will just make this the default layout. I do not like the value to be bdc for obvious reasons.
@@ -7,7 +7,6 @@ server.port=80 | |||
|
|||
dashboard.enable.extra_details=true | |||
dashboard.enable.bdc_hack=true |
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.
just use default layout
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.
Out of scope for this work. I wouldn't build a repository layer here. I would move the repository logic to the dataset repository.
No description provided.