-
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
Feature/editing iterative improvements #21
Conversation
timwekkenbc
commented
Aug 12, 2024
- Renamed and reorganized components to be easier to understand
- Directly navigate to rule manager page so there is no delay on load
- Rename main page
- Update header to be properly responsive
- Fix issue where rule with long json name bugs out sending it for review
- Add check to make sure inputed file path/name somewhat valid and is json when creating a new rule
- Show "bulk scenarios" for inReview and Published (but not embedded)
- Fix issue with linked rules not showing up properly anymore
- Fix issues with being able to change linked rule when not in edit mode
…ng json name bugs out sending it for review, Add check to make sure inputed file path/name somewhat valid and is json when creating a new rule, Show "bulk scenarios" for inReview and Published (but not embedded), Fix issue with linked rules not showing up properly anymore, Fix issues with being able to change linked rule when not in edit mode
…ly navigate to rule manager page so there is no delay on load, Rename main page
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.
The refactoring and reformatting done in this update are amazing! It really improves the clarity and organization of the code base. Makes it super easy to identify how this project functions on the frontend.
Looks really clean!
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.
Really happy with this being refactored into its own component.
@@ -44,7 +44,22 @@ export default function NewRule() { | |||
<Form.Item | |||
label="File path/name" | |||
name="goRulesJSONFilename" | |||
rules={[{ required: true, message: "Please input your JSON file path!" }]} | |||
rules={[ |
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.
Great clarification for the naming requirements. The active validation is so great! Would additional helper text indicating the formatting requirements ahead of time also be helpful? Something like:
help="example: my-rule.json or my-path/my-rule.json"
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.
Yeah, good idea. For some reason the "help" parameter overrides any error messages, so I'm going to add it as a tooltip because that's easy