Nechal Maggon
Nechal Maggon
With the introduction of workspace constants there is no longer a requirement for workspace variables. Hence, they need to be deprecated.
**Background**- With the introduction of workspace constants, there is no longer a requirement for workspace variables. There already is an info message stating that it will be deprecated and urging...
**Current scenario/Problem statement**- Data sources are categorized based on type and sorted alphabetically for ease of use. However, with the variety of data sources available, the most commonly used data...
**Problem statement-** When a user is in dark mode, the loading state still shows in light mode. Design file- https://www.figma.com/file/SZKm4ecuzgBwFq0v4sfrO5/Sanitation?type=design&node-id=5439-7625&mode=design&t=0gqfIETTy714VZuG-0
Without a loading state- the user is not able to tell when changes are complete and if they can perform the next action or not. https://github.com/ToolJet/ToolJet/assets/127945292/8e91d494-ac32-4b4c-8aba-f5328b580e55
App name edits should be reflected in the exported app https://github.com/ToolJet/ToolJet/assets/127945292/1e038159-f2d5-4dac-b07b-3c2afb9153e9
When a user creates a template and then creates a new version from it, duplicate queries are created. This could be due to Local Data sources.
Copywriting to be updated as- `We have launched workspace constants and sunsetting workspace variables very soon. Please migrate workspace variables immediately to safeguard your applications from this breaking change. Please...
Fix is provided- waiting for it to be tested to confirm it's working