* Issue 858: On the new calendar page adding a new Date entry with the "Add" button will now insert a new date with an offset of +24 hours of the previous row's date value.
* Added comment to ignore the TSLint "object can be null" error
* Changed `var` to `const`
* Fixed Prettier checks in CI pipeline
* Fixed Typecheck CI pipeline error
* Moved getDateWithHoursOffset() function to app/utils/dates.ts
* Added new line at end of file
* Added getValidNewDateIfInvalid() function. This retrieves a valid date. If invalid, get a new Date object.
- So now, if we intentionally/accidentally delete the data in the Calendar's DateInput element, it will be reset to the current Date/Time
* Refactored DateInput component's update state mechanism to be handled by an onChange() function defined in the parent component that is passed to the child
* Prettier formatting so that the new CI pipeline won't output errors at me
* Removed unused imported types
* Removed the datesCount React Hook & refactored accordingly
* Removed unused loader-related variables
* DateInput onChange prop is now optional
* Instead of generating a new Array, iterate over DateInput's inputState's array instead
* Fix potential undefined error
* DatesInputState: refactored to remove index & access the index during iteration with map() 2nd arg
* Properly initialized state for pre-existing events =)
- Also added TODO comments for improving date input handling (1082)
* Prettier formatting
* Uncommented console.warn()
* Touched up comment
* Passed a FUSE_OPTIONS object to the Fuse() object.
- We can now adjust how "strict" the search is.
* Refactored Combobox to accept an optional fuseOptions object as a prop
* Fixed fuseOptions prop data type & added a default initialized value of {}
- Moved the USER_COMBOBOX_FUSE_OPTIONS outside of the function
* Issue 1036: non-draggable ability icons will no longer have its cursor morphed to a pointing hand icon
* Revert "Issue 1036: non-draggable ability icons will no longer have its cursor morphed to a pointing hand icon"
This reverts commit a0de4e0047.
* Issue 1036: Non-draggable ability icons will no longer have its cursor morphed to a pointing hand icon.
- Done correctly by conditionally choosing to render a <button /> or <div /> HTML element for ability icons everywhere Ability() was invoked by passing in readonly
* Removed stray console.warn() line, added a brief comment
* Removed unnecessary tabIndex adjustment for AbilityTag element if it is readonly (since it is no longer rendered as a button if it is readonly)
- We now also condtionally give type="button" to AbilityTag only if it is actually a button
* Conditionally set AbilitiesSelector's Ability JSX elements to readonly if the ability is "UNKNOWN"
* Fixed failed check for Prettier in CI pipeline
* Ability component now only chooses the readonly class if no onClick function is passed into it
- Exception: if the ability is "UNKNOWN", it will be forced to readonly
* Fixed Prettier error in CI pipeline
* Fixed Typecheck error in BuildCard.tsx
* Fixed Prettier CI pipeline error again
* Was checking for an undefined type incorrectly. Now the logic works properly
* Fixed Prettier error
* Cleaned up classname declaration syntax to React's shorthand
Planned to be replaced with Playwright maybe?
Just removing in the meanwhile so they don't confuse people.
Or that people won't accidentally develop new.
- Do not allow dragging an ability onto a slot that cannot accept that
ability.
- When dragging, dim slots that are not a valid target for the ability
currently being dragged.
- Do not make any changes to the existing click behavior to assign
abilities.
`<Ability/>` can now be tabbed through, and it now shares the same focus
outline, hover, and mousedown styles with `<AbilitiesSelector/>`. This
includes the `cursor: pointer` style that makes it more obvious that
this component is clickable like other buttons.
Fixes#894.
