×
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 år 6 månader sedan #837
av Walt Sorensen
Feature requests skapades av 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.
Be Logga in eller Skapa ett konto ansluta till konversationen.
Tag Websites
New Member
Posts: 2
9 år 2 månader sedan #1023
av Tag Websites
Svar från Tag Websites i ämnet Feature requests
Yes - definitely - Conditional fields would be great.
Be Logga in eller Skapa ett konto ansluta till konversationen.
Andres Maeso
Platinum Member
Posts: 338
9 år 2 månader sedan #1030
av Andres Maeso
Andrés Maeso
Customer relations manager at Joomla Component Creator.
Den här e-postadressen skyddas mot spambots. Du måste tillåta JavaScript för att se den.
Svar från Andres Maeso i ämnet 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.
Den här e-postadressen skyddas mot spambots. Du måste tillåta JavaScript för att se den.
Be Logga in eller Skapa ett konto ansluta till konversationen.
Phil
New Member
Posts: 1
9 år 1 månad sedan #1036
av Phil
Svar från Phil i ämnet 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.
Be Logga in eller Skapa ett konto ansluta till konversationen.
Walt Sorensen
Senior Member
Posts: 54
9 år 1 vecka sedan - 9 år 1 vecka sedan #1092
av Walt Sorensen
Svar från Walt Sorensen i ämnet 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 år 1 vecka sedan by Walt Sorensen. Orsak: links to the breakout of requests from this post
Be Logga in eller Skapa ett konto ansluta till konversationen.
Sidan laddades på: 0.057 sekunder