-
Notifications
You must be signed in to change notification settings - Fork 106
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
dynamic batch connect apps #851
Labels
area/installation
component/batch_connect
enhancement
This is functionality that builds upon existing functionality.
epic
Very large tickets
Milestone
Comments
I'm going to break this ticket up. options for handlers were added in #1380, we'll make other tickets for other features. |
This was referenced Oct 1, 2021
johrstrom
changed the title
Add javascript helpers for commonly used patterns in batch connect apps
dynamic batch connect apps
Apr 25, 2022
lukew3
added
the
enhancement
This is functionality that builds upon existing functionality.
label
Jun 30, 2022
Oglopf
added
component/dashboard
bug
Existing functionality not working as expected
and removed
bug
Existing functionality not working as expected
component/dashboard
labels
Dec 5, 2022
This is actually in 2.0 as well, but will be in 2.1 with some bugfixes that 2.0 may not have. |
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/installation
component/batch_connect
enhancement
This is functionality that builds upon existing functionality.
epic
Very large tickets
I know we've talked about this, but I don't know if there's any ticket for the actual feature. Looks like we worked on #513 but decided against it, though I'm not sure if we decided against the approach in the PR or the idea altogether.
We have a similar approach in our own BC apps, so maybe our jquery javascript approach may be mature enough.
I think the result could be something like setting for node types.
data-option-for-<ATTRIBUTE>-<ATTRIBUTE VALUE>
data-[min,max]-<CORES ATTRIBUTE>-for-<CHANGE ATTRIBUTE>-<ATTRIBUTE VALUE>
CORES ATTRIBUTE
whenCHANGE ATTRIBUTE
is set toCHANGE ATTRIBUTE VALUE
.These are common patterns we see all the time, needing to hide something based off of a selected value and changing mins and maxes. Is this approach generic enough to pick up other use cases? maybe not, but maybe we don't need to worry about every use case just yet. This may provide a lot of value for folks.
Here's what's complete and what's still to do.
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: