docs: rewrite pattern matching documentation#58
Open
arthursimas1 wants to merge 4 commits intoasterisk:mainfrom
Open
docs: rewrite pattern matching documentation#58arthursimas1 wants to merge 4 commits intoasterisk:mainfrom
arthursimas1 wants to merge 4 commits intoasterisk:mainfrom
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR proposes a rewrite in the pattern matching documentation for better clarity and organization.
I first started to fix the final section about Matching on Caller ID, but then I realized that the whole document could be further improved.
I'm willing to change it based on your suggestions.
I need some clarification:
The only characters with special meaning within a set are the '-' character, to define a range between two characters, the '\' character to escape a special character available within a set, andWhat is the other character with special meaning? Notice the final and ...
Please be aware that because of the way auto-fallthrough works, if Asterisk can't find the next priority number for the current extension or pattern match, it will also look for that same priority in a less specific pattern match.If I write it as "it will look for that next priority in a less specific pattern match", does it still represents the correct behaviour? I thought it's clearer.
Only
!is used for overlap dialing or.can also be used? Is this the difference that the old text was talking about?I couldn't find nothing regarding overlap dialing on the Asterisk docs. Does this page exist? We could link it here. If it's missing, we can write something in that matter (example)
Resolves: #56