-
Notifications
You must be signed in to change notification settings - Fork 241
Dev > Main for v2.4.6 #1176
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
Merged
Merged
Dev > Main for v2.4.6 #1176
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix 500 issue when cookie expires
…pmRegistries [WIP] Enable private npm registries
chore: Deploy to Elestio button updated
…y proxy and package cache
fix issue with lastEditedAt
get editingUserId, lastEditedAt on get endpoint
fix js query to mark ready for itself as dependency
set editingUserId, lastEditedAt on put endpoint, get editingUserId, lastEditedAt on get endpoint
fix overwriting issue on lastEditedAt
Concurrency user display
✅ Deploy Preview for lowcoder-test canceled.
|
✅ Deploy Preview for lowcoder-cloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
After a fruitful summer full of hard work, we are pleased now to present v2.4.6 of Lowcoder.
Next to many bugfixes and improvements we have done a long list of fantastic new features!
New Translations
Automatic updated (completed) existing languages - based on EN as master file.
We have now Chinese, English, Italian, Spanish, Portuguese, German, Russian. More languages will follow.
Table with up to 3 Summary rows.
One can now add up to 3 empty rows, that are unconnected to the data source and fill it with summary calculations or
status / progress displays for example. We decided to offer up to 3 for “SUM”, “TAX” and “TOTAL” for example. Data
Calculations can be done for each column based on the bound table data object for example. But also other queries
could get used.
Table Edit mode with single click and tab-key navigation
Till now to edit data in a table was truly a bad experience. Every value in a column needed to be double clicked to
“activate” an Edit-Mode. Now we lift that, so users can save a lot of time for fast data edit in tables. Based on tab they
can skip trough the columns and rows and auto-activate the edit mode. Also the App Creator can select between “Single
Click” or “Double click” to activate the Edit Mode in the Table Cells.
New Record Edit Rows
The Current table only supported the editing of existing Rows (so you can UPDATE). Now the App Creator can activate a
new row type which is always displayed at the end of the table to enable users to enter new records. These data is
accessible as table.toInsertRows and by this the App Creator can bind this data to an different Data Query (INSERT for
example)
Timezone for Date, Date-Range, Time, Time-Range.
The App Editor can now set a timezone for these components as default or let it up to the User to select not only date
and time, but also the corresponding timezone. time.timeZone will give then a JSOPN object containing Information
about the user-selected Timezone and in the time.formattedValue the timezone is accordingly named.
Calendar Update with Tab-Modal
More fine graded control for the Event Data Entry at the calendar. Also Colors now also for “past events”, just with a
small “grey layer”, so it is visually to see that these events are in the past.
Kanban Component (EXPERIMENTAL - not yet for productive use)
The Kanban Component is in EXPERIMENTAL State - and only meant as preview. However, it demonstrates the abilities
by the possibility to place Lowcoder Components inside the Kanban Card Display - which opens up endless possibilities
how to use the Kanban Component.
Changed the whole Remote Comps Repository to a “private hosted” Repository mechanism.
Now not only components like the Calendar are hosted directly with the Lowcoder installation and therefore can get loaded
much faster - but also an App Creator and his company can operate and use a “private NPM” Repository for
their individual Component Plugins - which also helps a lot for Component Plugin Development.
Added Supabase SDK natively,
so App Creators can now use the Supabase Client SDK fully in their Apps.
Added better Scrollbar Control
(dynamic or static switched) to show/hide Scrollbars (vertical / horizontal
independently) for many Components like Table, Container…
Concurrent App Editing Display
If a User A edit an Lowcoder app, and another User B also opens the very same app to edit, both would end up in
concurrent overwriting of the app Edit states - as Lowcoder as for now only was made for a single-user as Editor. In our
first attempt to support better multi-user (Editor) experience, we introduce with this PR a optimistic locking strategy. We
think it is not a true way to go to try to get a real "multi-user interactivity" for app editing to work. It is not really the case
that 2 people same time want collaborative want to edit a single app. Still it can happen that by accident and as rather
rare case 2 users open an app independently in the same time. In this PR we introduce a display for "User B" to get a
notice, that a "User A" is editing the app. After a time window of 3 minutes of inactivity of User A - the lock will be
removed and User B can go on to edit the app.
App Re-Rendering minimized
We invested (and will invest further) time to optimise and especially to speed up the App rendering, so the overall
experience will be faster for the App User.
Controllable Waiting Indicators
We unified the various waiting indicator types to now only show “Skeletons” for all components. This helps to “calm” the
visual impression of App Loading state. By the Themes, we added the possibility to generally activate or deactivate the
Loading Display for “App Loading” and “Data Query Loading”.
page title in Browser Tabs
opened by a User
“currentUser” to logout himself.
utils.logoutUser()
Types of changes
Checklist