×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Feature requests
Walt Sorensen
Senior Member
Posts: 54
9 years 6 months ago #837
by Walt Sorensen
Feature requests was created by Walt Sorensen
Here is the list I included in my "other features" for the features survey that I had not posted here nor did I see in the forum.
9. relation/conditional field types
display a selection list using relations tables and/or conditionals for the fields
11. Connect to _____ service
It would be nice if there was some popular services that components could connect to using REST etc ( www.webdesignerdepot.com/2011/07/40-usef...ners-and-developers/ )
12. GitHub integration (build and upload a push to a github repository)
github.com/integrations
13. Travis CI integration
Like github it would be helpful for a pre-build to be tested on travis ci before download
docs.saucelabs.com/ci-integrations/travis-ci/
14. add unit tests
I would love to see default unit tests for builds and an option for me to write custom unit tests for
custom fields. (somewhat connects to the Travis CI integration and Github integration)
15. Better versioning control work flow
When I "copy" a component rather that automatically adding "copy" to the name, ask us if we want to bump the version number of the component or "fork" with new name.
9. relation/conditional field types
display a selection list using relations tables and/or conditionals for the fields
11. Connect to _____ service
It would be nice if there was some popular services that components could connect to using REST etc ( www.webdesignerdepot.com/2011/07/40-usef...ners-and-developers/ )
12. GitHub integration (build and upload a push to a github repository)
github.com/integrations
13. Travis CI integration
Like github it would be helpful for a pre-build to be tested on travis ci before download
docs.saucelabs.com/ci-integrations/travis-ci/
14. add unit tests
I would love to see default unit tests for builds and an option for me to write custom unit tests for
custom fields. (somewhat connects to the Travis CI integration and Github integration)
15. Better versioning control work flow
When I "copy" a component rather that automatically adding "copy" to the name, ask us if we want to bump the version number of the component or "fork" with new name.
Please Log in or Create an account to join the conversation.
Tag Websites
New Member
Posts: 2
9 years 2 months ago #1023
by Tag Websites
Replied by Tag Websites on topic Feature requests
Yes - definitely - Conditional fields would be great.
Please Log in or Create an account to join the conversation.
Andres Maeso
Platinum Member
Posts: 338
9 years 2 months ago #1030
by Andres Maeso
Andrés Maeso
Customer relations manager at Joomla Component Creator.
This email address is being protected from spambots. You need JavaScript enabled to view it.
Replied by Andres Maeso on topic Feature requests
Hey Walt
Thanks for all your suggestions. Those are great ideas but I think a post per idea would be great, this way other users that feel like they could use that feature can +1 it.
Best regards
Thanks for all your suggestions. Those are great ideas but I think a post per idea would be great, this way other users that feel like they could use that feature can +1 it.
Best regards
Andrés Maeso
Customer relations manager at Joomla Component Creator.
This email address is being protected from spambots. You need JavaScript enabled to view it.
Please Log in or Create an account to join the conversation.
Phil
New Member
Posts: 1
9 years 2 months ago #1036
by Phil
Replied by Phil on topic Feature requests
I would like to add to the list:
1) When defining a field, create an automatically generated default code (like a password or coupon etc.)
2) You need an action step. When the user submits the form, there needs to be a validation and condition phase. If this matches that, go to this page; If this contains that, do this;
3) You need an ending page. You can't just ask users to enter info and then go nowhere.
1) When defining a field, create an automatically generated default code (like a password or coupon etc.)
2) You need an action step. When the user submits the form, there needs to be a validation and condition phase. If this matches that, go to this page; If this contains that, do this;
3) You need an ending page. You can't just ask users to enter info and then go nowhere.
Please Log in or Create an account to join the conversation.
Walt Sorensen
Senior Member
Posts: 54
9 years 1 week ago - 9 years 1 week ago #1092
by Walt Sorensen
Replied by Walt Sorensen on topic Feature requests
Andres
, I'll break this up into single requests.
here is the list
www.component-creator.com/en/forum/featu...ditional-field-types
www.component-creator.com/en/forum/featu...rvice-using-rest-etc
www.component-creator.com/en/forum/featu...4-github-integration
www.component-creator.com/en/forum/featu...ravis-ci-integration
www.component-creator.com/en/forum/featu...uests/416-unit-tests
www.component-creator.com/en/forum/featu...ng-work-flow-control
here is the list
www.component-creator.com/en/forum/featu...ditional-field-types
www.component-creator.com/en/forum/featu...rvice-using-rest-etc
www.component-creator.com/en/forum/featu...4-github-integration
www.component-creator.com/en/forum/featu...ravis-ci-integration
www.component-creator.com/en/forum/featu...uests/416-unit-tests
www.component-creator.com/en/forum/featu...ng-work-flow-control
Last edit: 9 years 1 week ago by Walt Sorensen. Reason: links to the breakout of requests from this post
Please Log in or Create an account to join the conversation.
Time to create page: 0.057 seconds