Activities of "rafael.gonzales"

No answers here

any answers for this, please?

In the Index.Js template, for example, Frontend.Mvc.Page.index.js.txt

We can add this as navigation dropdowns, if anyone wants to use typeahead because they have high volume in their dropdowns, in the Index Page, we are forced to use traditional approach of getting the information in the Razor Pages and then bind the control, why can't we use typeahead in the Index.cshtml too?

To accomplish that, we might start by adding this to work in the index.js and change the HTML generated in the index.cshtml %%navigation-property-dropdown-methods%%

Would it be possible to add another template?

In "Server.AppService.AppService.txt", there is a KEYWORD for navigation repositories

For property declaration %%navigation-property-repositories%%

For constructor %%navigation-property-repositories-inject%%

And for variable assignation from constructor %%navigation-property-repositories-ctor%%

This will generate IRepository<MyEntity, MyPrimaryKeyType> but what if we want to use the exact repository and instead of using this autogenerated, we want to use IMyEntityRepository which is also generated by ABP Suite.

Can you give us that control to customize which repository we will use by default? if the generic one or the already generated one.

Thanks

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.

When generating a demo entity with Byte as a type, the demo test includes this in the EntityApplicationTests.cs file trying to match a byte with a method that requires an integer

This is just a demo project. My real project has the requirement to have dropdowns at the beginning

Hi Liangshiwei,

It still happens if you have, for example, a dropdown as a first control. I made a loom video for that. How can you handle that situation? https://www.loom.com/share/6bcadeb599ac4a519e7f14b68c5098b0?sid=e1486af3-9d5d-4585-b93e-80f449cd5c45

But this is not the expected behavior. The data is not being bonded to the control and the style and functionality are not the same as using the <abp-date-picker> tag. It should be an option in the same abp-date-picker tag to activate or deactivate the automatic opening of the datepicker. Using the <abp-input> as a workaround forces me not to use what abp can offer me from its core and makes me handle the bootstrap datetimepicker activation by my self and the data binding which is not what we are looking for.

Typeahead not rendering in the correct position when It's within a long modal content

I found a fix for this, following the different recommendations from this post https://stackoverflow.com/questions/18487056/select2-doesnt-work-when-embedded-in-a-bootstrap-modal/19574076#19574076 and select2 documentation https://select2.org/troubleshooting/common-problems#:~:text=Select2%20does%20not%20function%20properly,%22outside%20of%20the%20modal%22.

The working solution for ABP Suite generated code it's to add " .modal-content" in the dropdownParent generated by ABP Suite.

Should look like this

        publicApi.onOpen(function () {
            $('#Demo_RelatedId').select2({
                dropdownParent: $('#DemoCreateModal .modal-content'),
                ajax: {
                    url: abp.appPath + 'api/app/demos/related-lookup',
                    type: 'GET',
                    data: function (params) {
                        return { filter: params.term, maxResultCount: 10 }
                    },
                    processResults: function (data) {
                        var mappedItems = _.map(data.items, function (item) {
                            return { id: item.id, text: item.displayName };
                        });

                        return { results: mappedItems };
                    }
                }
            });
        });

Hope you can add it to the next RC.

Thanks!