Sorry my mistake. It means white spaces character not spaces
2018년 6월 6일 수요일 오후 6시 3분 48초 UTC+9, Florian Apolloner 님의 말:
>
>
>
> On Tuesday, June 5, 2018 at 4:30:03 AM UTC+2, oli...@kidsnote.com wrote:
>>
>> allowing spaces can be done by simply adding \s* after (arg_sep)s
>>
>
> \s is __not__
On Tuesday, June 5, 2018 at 4:30:03 AM UTC+2, oli...@kidsnote.com wrote:
>
> allowing spaces can be done by simply adding \s* after (arg_sep)s
>
\s is __not__ the regex for spaces
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions
filter_raw_string = r"""
^(?P%(constant)s)|
^(?P[%(var_chars)s]+|%(num)s)|
(?:\s*%(filter_sep)s\s*
(?P\w+)
(?:%(arg_sep)s
(?:
(?P%(constant)s)|
(?P[%(var_chars)s]+|%(num)s)
)
)?
)""" % {
'constant':
filter_raw_string = r"""
^(?P%(constant)s)|
^(?P[%(var_chars)s]+|%(num)s)|
(?:\s*%(filter_sep)s\s*
(?P\w+)
(?:%(arg_sep)s
(?:
(?P%(constant)s)|
(?P[%(var_chars)s]+|%(num)s)
)
)?
)""" % {
'constant':
Currently, spaces between filter separator( | ) and filter name is allowed.
Also, value name and filter separator.
So, following is allowed.
{{ value|filter:"arg" }}
{{ value|filter:"arg" }}
But, following is not allowed.
{{ value|filter: "arg" }}
users are confused by the
2018년 6월 5일 화요일 오전 10시 52분 16초 UTC+9, oli...@kidsnote.com 님의 말:
>
> Currently, django template system allow spaces between filter separator
> and filter name, also value name and filter separator.
> So, following is ok.
>
> {{ value|filter:"arg" }}
> {{ value|filter:"arg" }}
>
Currently, django template system allow spaces between filter separator and
filter name, also value name and filter separator.
So, following is ok.
{{ value|filter:"arg" }}
{{ value|filter:"arg" }}
But, following can't be parsed
{{ value|filter: "arg" }}
I think that this
On 05/31/2018 06:39 PM, oli...@kidsnote.com wrote:
Are there any reasons that not allow spaces between separator and arg?
My first thought would be that it starts making the syntax looser,
meaning more things that are currently error cases would be accepted as
valid.
Which means mistakes
On Friday, 1 June 2018 03:06:01 UTC+1, Collin Anderson wrote:
> Maybe it would be worth having a more friendly error message?
>
>
I agree, it would be good to improve the message.
I've also seen users confused by the "could not parse the remainder"
message when they forget the spaces around
Maybe it would be worth having a more friendly error message?
On Thu, May 31, 2018 at 8:59 PM, wrote:
> Thank you for your reply.
> I understand your opinion well
>
> 2018년 5월 31일 목요일 오전 11시 41분 22초 UTC+9, oli...@kidsnote.com 님의 말:
>>
>> In the template filter system now,
>>
>> spaces between
Thank you for your reply.
I understand your opinion well
2018년 5월 31일 목요일 오전 11시 41분 22초 UTC+9, oli...@kidsnote.com 님의 말:
>
> In the template filter system now,
>
> spaces between augment separator and augments generate error.
> For example, the following template code generates the following
On Thu, May 31, 2018 at 1:39 AM, wrote:
> Are there any reasons that not allow spaces between separator and arg?
>
Every optional variant of template syntax is a potential source of bugs or
compatibility issues for the future. And a potential source of confusion
when someone is trying to learn
Are there any reasons that not allow spaces between separator and arg?
2018년 5월 31일 목요일 오전 11시 41분 22초 UTC+9, oli...@kidsnote.com 님의 말:
>
> In the template filter system now,
>
> spaces between augment separator and augments generate error.
> For example, the following template code generates the
I think it's better to be conservative here and leave it as-is, the current
syntax has worked for years and this change doesn't really reduce the risk
of bugs.
On Thu, 31 May 2018 at 03:34, wrote:
> In the template filter system now,
>
> spaces between augment separator and augments generate
14 matches
Mail list logo
