Skip to content
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

Minor fixes before making an official V1.0 release #1251

Merged
merged 4 commits into from
Dec 11, 2024

Conversation

stevecassidy
Copy link
Contributor

Minor fixes before making an official V1.0 release

JIRA Ticket

None

Description

Just fixing up any minor things before finalising the 1.0.0 release.

Proposed Changes

  • Auto-incrementer field editor was too strict in checking values and didn't allow deleting of current value
  • Auto-incrementer sometimes didn't get the existing ranges, I think because of the initial value in useQuery

How to Test

Check that all of the above are working well on mobile.

Checklist

  • I have confirmed all commits have been signed.
  • I have added JSDoc style comments to any new functions or classes.
  • Relevant documentation such as READMEs, guides, and class comments are updated.

Copy link
Contributor

@PeterBaker0 PeterBaker0 left a comment

Choose a reason for hiding this comment

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

Looks minor - I haven't tested but not too concerned about auto-incrementers at this stage. Pretty opposed to the number | string setup but it's minor.

Comment on lines +211 to +212
const [start, setStart] = useState<number | string>(props.range.start);
const [stop, setStop] = useState<number | string>(props.range.stop);
Copy link
Contributor

Choose a reason for hiding this comment

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

do they really need to be a number or a string? Might be better to on each render parse the value as a number - just choose one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is to allow for the empty string, if I don't, you can't delete the number that's there to enter a new one. Note this is only for the field value, not for the final data structure which is a number.

Signed-off-by: Steve Cassidy <steve.cassidy@mq.edu.au>
Signed-off-by: Steve Cassidy <steve.cassidy@mq.edu.au>
Signed-off-by: Steve Cassidy <steve.cassidy@mq.edu.au>
Now fixed in another PR.

Signed-off-by: Steve Cassidy <steve.cassidy@mq.edu.au>
@stevecassidy stevecassidy merged commit 00f9de5 into main Dec 11, 2024
2 checks passed
@stevecassidy stevecassidy deleted the pre-release-v1-fixes branch December 11, 2024 20:53
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