Fixing references to the github issue tracker.
Loading branch information
2 changed files
and 3 deletions.
@@ -20,7 +20,7 @@ layout: page.twig
li>Send a pull request</ li>
- We have an issue tracker
on < a href= " https:// github.com /proem/proem/issues " >Github</ a>, pick a ticket and resolve it. If there
+ We have an issue tracker
hosted by < a href= " http:// atlassion.com " >Atlassian</ a > at < a href = " https://proemframework.atlassian.net " >https://proemframework.atlassian.net</ a>, pick a ticket and resolve it. If there
is something you want to work on and a ticket doesn't exist for it yet, create one.
@@ -178,7 +178,7 @@ layout: docs.twig
These basically take the place of the <
em>echo "in Event1</ em> and < em>echo "out Event1</ em> parts of the simple example above.
div class= > "alert alert-notice "
- The Filter Component itself is yet to be documented, however it
< a href = " https://github.com/proem/proem/issues/80 " >is planned </ a >.
+ The Filter Component itself is yet to be documented, however it is planned.
So, with all that in mind hopefully you can see that the Proem object's init() method executes the following process:
@@ -342,7 +342,7 @@ layout: docs.twig
I can also hear people screaming that "by the time I listen for all these events my bootstrap is going to be a mess!". While this might look like the case at this
point in time there are already processes in place to work around this. The <
a href= >Ext</ "https://github.com/proem/proem/tree/develop/lib/Proem/Api/Ext " a> name space
adds the ability to load <
em>Plugins</ em> and < em>Modules</ em> that are used to group event listeners into self contained name spaces of code that you can load into
- your bootstrap (this stuff is just
< a href = " https://github.com/proem/proem/issues/80 " >yet to be documented </ a >).
+ your bootstrap (this stuff is just yet to be documented.
There is also likely to be some form of configuration layer added over the top of the Bootstrap when the current API becomes a little more stable.