Skip to content
This repository was archived by the owner on Aug 31, 2021. It is now read-only.

[Bug 18353] Remove duplicated urlResponse documentation#4880

Merged
peter-b merged 1 commit into
livecode:develop-8.1from
peter-b:bugfix-18353
Nov 16, 2016
Merged

[Bug 18353] Remove duplicated urlResponse documentation#4880
peter-b merged 1 commit into
livecode:develop-8.1from
peter-b:bugfix-18353

Conversation

@peter-b

@peter-b peter-b commented Nov 15, 2016

Copy link
Copy Markdown
Contributor

The urlResponse was documented twice, once as a function and once as
a property. This patch removes the function form, because the engine
source code treats the urlResponse as a property.

The `urlResponse` was documented twice, once as a function and once as
a property.  This patch removes the function form, because the engine
source code treats the `urlResponse` as a property.
@peter-b peter-b added this to the 8.1.3-rc-1 milestone Nov 15, 2016
@livecodeali

Copy link
Copy Markdown
Member

@livecode-vulcan review ok 2dd1bee

@livecode-vulcan

Copy link
Copy Markdown
Contributor

💙 review by @livecodeali ok 2dd1bee

@livecodeali livecodeali mentioned this pull request Nov 16, 2016
livecode-vulcan added a commit that referenced this pull request Nov 16, 2016
[Bug 18353] Remove duplicated urlResponse documentation

The `urlResponse` was documented twice, once as a function and once as
a property.  This patch removes the function form, because the engine
source code treats the `urlResponse` as a property.
@livecode-vulcan

Copy link
Copy Markdown
Contributor

😎 test success 2dd1bee

@peter-b peter-b merged commit 5831242 into livecode:develop-8.1 Nov 16, 2016
@peter-b peter-b deleted the bugfix-18353 branch November 16, 2016 10:12
livecode-vulcan added a commit that referenced this pull request Nov 16, 2016
[[ Docs ]] Fix typo

Fix a type I discovered when checking the doc related to #4880
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants