-
Notifications
You must be signed in to change notification settings - Fork 1
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
Added spec for dependent fields in expesnse rules #546
Conversation
generalpy101
commented
Sep 18, 2024
reference/admin.yaml
Outdated
parent_expense_field_id: | ||
type: integer | ||
description: | | ||
This id provided by Fyle to identify an expense field. |
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.
This id provided by Fyle to identify an expense field. | |
This id provided by Fyle to identify the parent expense field. |
reference/admin.yaml
Outdated
dependent_expense_field_id: | ||
type: integer | ||
description: | | ||
This id provided by Fyle to identify an expense field. |
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.
This id provided by Fyle to identify an expense field. | |
This id provided by Fyle to identify the dependent expense field. |
reference/approver.yaml
Outdated
parent_expense_field_id: | ||
type: integer | ||
description: | | ||
This id provided by Fyle to identify an expense field. |
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.
same comments as above
src/components/schemas/fields.yaml
Outdated
parent_expense_field_id: | ||
type: integer | ||
description: | | ||
This id provided by Fyle to identify an expense field. |
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.
same as above
PR title must start with "fix:", "feat:", "chore:", "refactor", or "test:" (case-insensitive) |
PR description must contain a link to a ClickUp (case-insensitive) |