39 Answer(s)
-
0
Add SignalR sample to both backend, gateway and Angular. Somehow with Micro Services template, the Angular SignalR request is always rejected by gateway and we couldn't figure out the reason.
AbpEntityChanges, add two properties which is JSON format old instance snapshot and new instance snapshot.
-
0
Add SignalR sample to both backend, gateway and Angular. Somehow with Micro Services template, the Angular SignalR request is always rejected by gateway and we couldn't figure out the reason.
AbpEntityChanges, add two properties which is JSON format old instance snapshot and new instance snapshot.
This is not a feature request for ABP Suite, please write these requests in the https://support.abp.io/QA/Questions/3052/Your-feature-request
-
0
Can you add information about the template used to create the solution and maybe a "Create another" dropdown option so I don´t have to wonder about this every time I create a new solution.
I use this when I do version updates. What I will do is to create another "compare" solution and then use BeyoundCompare to compare all the files and see if there are some other changes or best practises I want to move over also.
-
0
Can you add information about the template used to create the solution and maybe a "Create another" dropdown option so I don´t have to wonder about this every time I create a new solution.
I use this when I do version updates. What I will do is to create another "compare" solution and then use BeyoundCompare to compare all the files and see if there are some other changes or best practises I want to move over also.
I created an internal issue in our system
-
0
I hope the Support Team will be able to add the 'Import Excel' feature to insert data into the grid from an Excel file on Blazor.
-
0
I have downloaded Abp suite version 8.1.0 but i still can't create a property of type "DateOnly" and "TimeOnly" inside an entity. When will this feature be available?
-
0
I have downloaded Abp suite version 8.1.0 but i still can't create a property of type "DateOnly" and "TimeOnly" inside an entity. When will this feature be available?
Hi, we have an internal issue for supporting
DateOnlyandTimeOnlytypes and we are aiming to introduce it with v8.2. -
0
When creating an entity with abp suite, in the appservice, use IReadOnlyRepository for lookup entities rather than IRepository so it wont be tracking the entity
-
0
Because the templates are not yet perfect and sometimes contain errors, I had to customize them. When a new version is released, it is relatively time-consuming to find out whether I can switch back to the original template, whether I have to continue using my modified template or whether I should even perform a merge.
Several possible solutions come to mind:
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
- Maybe it would also be a solution to store the original file in the same directory with a different file extension (.suite/customized-templates/Frontend.Blazor.Page.Item.razor.original.txt), then you would be able to see very well in Git whether changes have been made in the original (new version) and you would also have the possibility to make a diff with your own changes.
- The "deluxe version" would be if you were to implement a merge tool with which we could update to a new version ;-)
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
-
0
Because the templates are not yet perfect and sometimes contain errors, I had to customize them. When a new version is released, it is relatively time-consuming to find out whether I can switch back to the original template, whether I have to continue using my modified template or whether I should even perform a merge.
Several possible solutions come to mind:
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
- Maybe it would also be a solution to store the original file in the same directory with a different file extension (.suite/customized-templates/Frontend.Blazor.Page.Item.razor.original.txt), then you would be able to see very well in Git whether changes have been made in the original (new version) and you would also have the possibility to make a diff with your own changes.
- The "deluxe version" would be if you were to implement a merge tool with which we could update to a new version ;-)
Thanks for the suggestion, I have created an internal issue for this feature request.
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
-
0
Because the templates are not yet perfect and sometimes contain errors, I had to customize them. When a new version is released, it is relatively time-consuming to find out whether I can switch back to the original template, whether I have to continue using my modified template or whether I should even perform a merge.
Several possible solutions come to mind:
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
- Maybe it would also be a solution to store the original file in the same directory with a different file extension (.suite/customized-templates/Frontend.Blazor.Page.Item.razor.original.txt), then you would be able to see very well in Git whether changes have been made in the original (new version) and you would also have the possibility to make a diff with your own changes.
- The "deluxe version" would be if you were to implement a merge tool with which we could update to a new version ;-)
Thanks for the suggestion, I have created an internal issue for this feature request.
I would add that we would need a button like "download Zip with all template"
- Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
-
0
I would like the resources (localized strings) to have better names (keys). Or that they could be customized.
The problem is as follows: You often have the same property names in different entities. For example Name, Description, Remark, IsActive, ... But now you might want to call the "Name" property "Customer name" in the customer views and translate Name as "Company name" in the company views. This currently requires a lot of manual adjustments (or you have to be extremely careful when regenerating and make manual adjustments again).
I have adapted the templates accordingly so that this is generated according to the following scheme:
@L["Entity:%%entity-name%%:%%property-name%%"]"This makes future updates of the templates very time-consuming for me ( this is why I asked for a better update option). Because there are about 28 templates that I had to modify. But a structured resource file was more important to me.
Possible solution: ...would be if you could also specify the resource key to be used for a property in the suite. As a default, you could use %%property-name%% as in the past, which would also ensure backwards compatibility. But you would have the option of overwriting this.
I have also given all common resources (generated by the suite) the prefix "Common" (e.g.
@L["Common:Update"]). This allows me to sort the resource file and see immediately which strings have been generated and belong together. These strings are defined in Frontend.Blazor.Page.Partials.Localizations.txt. -
0
Can you give us more flexibility in abp suite - template system? Like, give us more detail to be used in our customization for example. If we are rendering the create or edit modal, give us the data types associated or if it's nullable or not so we can create or adapt third-party library or more logic.
-
0
I would like native support for managing GeoJSON records with the different types & Longitude / Latitude fields in MongoDB.
For example to specify a GeoJSON Point:
location: { type: "Point", coordinates: [-73.856077, 40.848447] }
There are different GeoJSON types: Point, LineString, Polygon (Single + Multiple), MultiPoint, MultiLineString, MultiPoligon, Geometry Collection
Additional information about GeoJSON: https://www.mongodb.com/docs/manual/reference/geojson/
