Skip to content

Conversation

@conorschofield
Copy link
Collaborator

Add caput log detail page:

  • Added Caput log detail page to pvinfo header
  • Allows search using pv name, user, or client
  • Fixed date search to trigger new search when a date range is selected

@conorschofield conorschofield marked this pull request as draft August 4, 2025 20:02
add using caputlog check for header navigation

add caputlog search layout component

add new line

add caputlogSearchConfig

require proptypes
@conorschofield conorschofield marked this pull request as ready for review August 4, 2025 22:17
@conorschofield conorschofield marked this pull request as draft August 5, 2025 19:18
@conorschofield conorschofield marked this pull request as ready for review August 6, 2025 00:47
Copy link
Contributor

@tynanford tynanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really nice!

A few other general comments

  • I would rather structure caputlogtable as a directory under components since it is a separate component from things on the pv details page. But if that messes up imports then it's not a big problem
  • I noticed some caputs in our table to the .PROC field of a PV which is nice to see. But they don't show up in the caputlog table for that individual PV. I wonder if the PV details caputlog page could search for both pvname and pvname.* to catch all changes to the EPICS dot fields
  • allowing wildcard PV name searches would be useful

import CalendarMonthIcon from '@mui/icons-material/CalendarMonth';
import DatePicker from "react-datepicker";
import "react-datepicker/dist/react-datepicker.css";
import "@elastic/react-search-ui-views/lib/styles/styles.css";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is really nitpicky so I can work on it in a separate PR. But I would rather have the search button and fonts match the styling of the rest of PV Info

https://www.elastic.co/docs/reference/search-ui/basic-usage

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've started a CaputLogSearchLayout.css to match the current styling of the rest of PV info, it is still a bit of a work in progress but it is matching better now.

{showSearchBox && (
<SearchBox inputProps={{ placeholder: "Search by PV Name, User, or Client" }} />
)}
<DatePicker
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might be nice to have a clear button for the date picker to reset it back to no date range

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added this in the most recent commit

@conorschofield
Copy link
Collaborator Author

Looks really nice!

A few other general comments

* I would rather structure caputlogtable as a directory under components since it is a separate component from things on the pv details page. But if that messes up imports then it's not a big problem

* I noticed some caputs in our table to the .PROC field of a PV which is nice to see. But they don't show up in the caputlog table for that individual PV. I wonder if the PV details caputlog page could search for both `pvname` and `pvname.*` to catch all changes to the EPICS dot fields

* allowing wildcard PV name searches would be useful

I've fixed the second point. I'm still working on restructuring caputlogtable as a directory under components

update search css, add date clear button

added initial search wildcard to caputlog accordian to search for pvName* to include searching for pvs with sufixes

restructure caputlog page to be a directory under components
@conorschofield
Copy link
Collaborator Author

Looks really nice!
A few other general comments

* I would rather structure caputlogtable as a directory under components since it is a separate component from things on the pv details page. But if that messes up imports then it's not a big problem

* I noticed some caputs in our table to the .PROC field of a PV which is nice to see. But they don't show up in the caputlog table for that individual PV. I wonder if the PV details caputlog page could search for both `pvname` and `pvname.*` to catch all changes to the EPICS dot fields

* allowing wildcard PV name searches would be useful

Caputlog main page has been restructured under components

add custom elasticsearch connector for * functionality. This will allow for * wildcard at the end of the search. Still working on implementing * as a wildcard anywhere in the search string.

use optional chain expression

fix date filter when searchTerm is used

remove unused initialSearchTerm and setSearch

remove console log statements

update caputlog search to work with * wildcard

fix caputlog prefix .* search, update examples

fix caputlog prefix .* search and update example screenshots
@sonarqubecloud
Copy link

@tynanford
Copy link
Contributor

Really nice, much better than having to open kibana!

@tynanford tynanford merged commit 7a05b74 into ChannelFinder:master Aug 26, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants