Hi Kamidu, This is the method which is given by the DataTable examples [1]. And yes if it's published back-end API call, it will be not a best practice. So yes you can overwrite it and customize to match your requirement.
[1] - https://datatables.net/examples/api/multi_filter_select.html Regards, Jerad On Tue, Feb 16, 2016 at 10:23 AM, Kamidu Punchihewa <sachi...@wso2.com> wrote: > Hi Jerad, > > Since we are using the data table extended library and its filtering > option where backend ajax option is enabled.We don't have the access to > perform the suggestion you have provided. > Which is "if this is causing any issue for back-end processing. We should > handle it from the back-end or* before we make the back-end cal*l". > > Handling the css selectors which is appended from one particular UI > library from a published backend API is not the best practise to follow. > Sending css selectors to a backend api via the library is not the > advisable either. > > We should address this and enable the backend filtering without the "^", > "$" or any css and frontend related characters/selectors from the data > table extended library. > > Thanks and Regards. > > Kamidu Sachith Punchihewa > *Software Engineer* > WSO2, Inc. > lean . enterprise . middleware > Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194> > > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > > On Tue, Feb 16, 2016 at 8:22 AM, Jerad Rutnam <je...@wso2.com> wrote: > >> Hi Kamidu, >> >> This is to fix *exact *match filtering in front-end level. "^" for >> starts and "$" for ends with, for more details check html selectors [1]. >> >> e.g. This will fix the issue where it shows "in*active*" queries when we >> filter for "*active*". >> >> And if this is causing any issue for back-end processing. We should >> handle it from the back-end or before we make the back-end call. >> >> [1] - http://www.w3schools.com/cssref/css_selectors.asp >> >> Cheers! >> Jerad >> >> >> On Mon, Feb 15, 2016 at 9:05 PM, Kamidu Punchihewa <sachi...@wso2.com> >> wrote: >> >>> Hi UI/UX Team, >>> >>> I have faced $subject when fitting data using the ajax method. >>> An "IllegalArgumentException" was thoun in the back end, and a datatable >>> error alert was prompt from the front end when a filtering was triggered. >>> >>> There was a mismatch in the expected uri format and the current uri >>> format given by the data table extended library.When comparing expected >>> backend call [1] with current backend call [2] there were two extra >>> characters included to the current uri. >>> >>> This causes due to the latest change which is listed below. >>> >>> Older version : >>> >>> column >>>> >>>> .search(val ? val : '', true, false) >>>> >>>> .draw(); >>>> >>>> >>> New version : >>> >>> column >>>> .search(val ? '^' + val + '$' : '', true, false) >>>> .draw(); >>> >>> >>> >>> Any reason for this latest change ? >>> >>> [1]. 'endpoint?draw=2&start=0&length=16&type*=data'* >>> [2]. 'endpoint?draw=2&start=0&length=16&type*=^data$'* >>> >>> Thanks and Regards. >>> Kamidu Sachith Punchihewa >>> *Software Engineer* >>> WSO2, Inc. >>> lean . enterprise . middleware >>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194> >>> >>> >>> Disclaimer: This communication may contain privileged or other >>> confidential information and is intended exclusively for the addressee/s. >>> If you are not the intended recipient/s, or believe that you may have >>> received this communication in error, please reply to the sender indicating >>> that fact and delete the copy you received and in addition, you should not >>> print, copy, retransmit, disseminate, or otherwise use the information >>> contained in this communication. Internet communications cannot be >>> guaranteed to be timely, secure, error or virus-free. The sender does not >>> accept liability for any errors or omissions. >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Jerad Rutnam* >> *Software Engineer* >> >> WSO2 Inc. >> lean | enterprise | middleware >> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com >> > > -- *Jerad Rutnam* *Software Engineer* WSO2 Inc. lean | enterprise | middleware M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
