> For the complete documentation index, see [llms.txt](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/change-log.md).

# Change Log

## 1.43

* fix issues with resource timeline view
  * resource area is now dynamically set by pixels 
  * resource area now updates appropriately when 
* added event[ border color as an option](broken://pages/-MfFoLh7OJoo_fd2YUa_)
* a[dded a calendar border option](/fullcalendar-plugin-suite/elements/calendar/actions/initialize.md#calendar-border)
* small calender start/end date/time lists are not required.
  * what is required is that you use one or the other. either enter is a dynamic data type and use the range field to set event times 
  * OR
  * use the 2 input lists for start/end times. 
    * this was used to link up the Time Slot Generator's Filtered Time Slots List with the small calendar to be able to display bookable times

## 1.42 

* forgot some updates
* added the date/time picker
* fixed the small calendar issues
* fixed bugs with the date/dots
* updated a lot of element text to clarify what goes where

## 1.36.4

* add option[ 'auto height' ](/fullcalendar-plugin-suite/elements/calendar/input-fields/extras.md#auto-height)to calendar element
* date picker calendar no longer requires events
* fixed bugs with datepicker

## 1.35.3

* fix data out when using action jump to date
* fix errors/bugs occurring when using go forward/go backward 1 time period

## 1.35.1

Date picker / mini calendar added

## 1.34.4

1. Fixed calendar height bug. calendar will render the size that you design it. 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/change-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.