refs #552 - added note about __file__ deprecation in 1.1
Showing
1 changed file
with
6 additions
and
0 deletions
... | @@ -70,6 +70,12 @@ Sometimes it's helpful to inspect a variable, especially Object contents. The :r | ... | @@ -70,6 +70,12 @@ Sometimes it's helpful to inspect a variable, especially Object contents. The :r |
70 | Localize yourself in modules | 70 | Localize yourself in modules |
71 | ---------------------------- | 71 | ---------------------------- |
72 | 72 | ||
73 | .. warning:: | ||
74 | |||
75 | .. deprecated:: 1.1 | ||
76 | |||
77 | As of 1.1, CasperJS uses PhantomJS' builtin `require` and won't expose the `__file__` variable anymore. | ||
78 | |||
73 | If you're creating Casper modules, a cool thing to know is that there's a special built-in variable available in every module, ``__file__``, which contains the absolute path to current javascript file (the module file). | 79 | If you're creating Casper modules, a cool thing to know is that there's a special built-in variable available in every module, ``__file__``, which contains the absolute path to current javascript file (the module file). |
74 | 80 | ||
75 | 81 | ... | ... |
-
Please register or sign in to post a comment